File Feature

Create a GitHub issue for a feature row in docs/features.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing feature row, or asks 'create issue for feature #N', 'file feature 47', 'mirror feature 32 to GH', 'this feature needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/features.md` row because it lacks `GH: #N`. Skip if status is `TODO` (promote to `PLANNED` first) or Notes contains `Mirror: no`.

49 stars 21 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lllyys/vreader --skill file-feature
Manual install
git clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/file-feature ~/.claude/skills/file-feature

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# File Feature Issue

Create a GitHub issue mirroring an existing row in `docs/features.md`, then update that row's Notes column with `GH: #N`. Mirror of `/file-bug` for the features tracker.

## Input

Parse the user's request to extract a single integer feature ID (e.g. from `/file-feature 47`, `file feature #47`, or `mirror feature 47 to GH`). If the user did not name an ID, ask before proceeding.

## Phase 0 — Pre-flight

1. **Argument check**: parse `$ARGUMENTS` as a single integer feature ID. Empty / non-numeric → print usage `/file-feature <id>` and STOP.

2. **`gh` auth check**: `gh auth status`. If unauthenticated → print and STOP.

3. **Repo check**: `gh repo view --json nameWithOwner -q .nameWithOwner`. If errors → print and STOP.

4. **Row lookup**: `grep -n "^| <id>[ |]" docs/features.md | head -1`. If empty → STOP.

5. **Mirror-required state check**: status must be one of `PLANNED`, `IN PROGRESS`, `DONE`, `VERIFIED`. If `TODO` (not yet planned), print `Feature #<id> is at TODO — promote to PLANNED first per AGENTS.md` and STOP.

6. **Mirror: no escape**: if the Notes column contains `Mirror: no`, print `Feature #<id> is marked Mirror: no — skipping per row directive.` and STOP cleanly.

7. **Existing-issue check**: if Notes already has `GH: #N`, print and STOP cleanly (idempotent).

## Phase 1 — Build the issue

From the row, extract `title` (cell 2), `area` (cell 3), `priority` (cell 4), `status` (cell 5), `notes` (cell 6).

Compose:
Read the full skill on GitHub

Details

Skill name
file-feature
Repository
lllyys/vreader
Path
.claude/skills/file-feature/SKILL.md
Repo updated
6 August 2026

FAQ

What does the File Feature skill do?

Create a GitHub issue for a feature row in docs/features.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing feature row, or asks 'create issue for feature #N', 'file feature 47', 'mirror feature 32 to GH', 'this feature needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/features.md` row because it lacks `GH: #N`. Skip if status is `TODO` (promote to `PLANNED` first) or Notes contains `Mirror: no`.

How do I install the File Feature skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill file-feature. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is File Feature popular?

It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.

Related skills

AI Coding Agents

49

lllyys/vreader

Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.

AI, LLMs & Agents21

Dispatch

49

lllyys/vreader

Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.

Git & Code Review21

Feature Workflow

49

lllyys/vreader

Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud

Productivity & Notes21

Freedom of Movement

113

Hmbown/Wizards-of-the-Ghosts

Freedom of Movement is for processes that should be moving but are caught in glue: locked files, blocked ports, circular dependencies, wedged jobs, or permissions that almost work. The skill is about diagnosing the restraint, then removing or routing around it without tearing the whole system apart. It favors unblocking over brute force.

Productivity & Notes11

Insight Trace

49

hw-native-sys/simpler

Generate a MindStudio Insight trace for any `kernel_entry(args)` style kernel in this repo — SPMD mix, AIC-only single-task (e.g. `aic_pv_matmul`), or AIV-only single-task (e.g. `aiv_softmax_prepare`). Use when the user asks to "produce/generate/run an Insight trace", "trace this kernel under msprof op simulator", or troubleshoot Insight trace collection. AICore-only replay path — bypasses AICPU orchestration. For PTOAS-style kernels, use [PTOAS msprof_op_simulator_usage_zh.md](https://github.com/hw-native-sys/PTOAS/blob/main/.claude/skill/msprof_op_sim_insight_skill.md) instead.

Productivity & Notes102

Fear

113

Hmbown/Wizards-of-the-Ghosts

Fear makes targets run from danger. The real-world version is structured pessimism: pre-mortem analysis, worst-case scenario generation, and risk amplification exercises that counteract the natural optimism bias in planning. Fear is the antidote to "it'll probably be fine.

Productivity & Notes11

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.