Pre-flight CodeRabbit + Codex review state on the current PR, autonomously judge each finding (apply / defer / skip with reasoning), commit, push, and loop until clean. Use when the user types /github-dev:cr-fix, says "auto-fix the review", "process CodeRabbit feedback", or "loop until clean". v2 adds Step 5…
Analyze the project's tech stack and structure, then create a standardized set of GitHub issue labels via gh label create. Use when the user types /github-dev:create-issue-label, says "create issue labels", or sets up a label taxonomy for a repo. Examines package.json, README, and code layout to classify labels by…
Break a large work item into context-completable GitHub sub-issues, define a 10-20 node architecture and workflow mapping, propose a milestone, and create the issues with gh. Use ONLY when the user explicitly types /github-dev:decompose-issue or asks to decompose or break down work into issues. Do NOT auto-fire from…
Run after a PR merges — clean up the local branch, sync tracking, integrate what merged into config + wiki, commit. Use when the user types /github-dev:post-merge, says "post-merge cleanup", "integrate PR learnings", or merged a PR. Identifies the merged PR (gh pr view is the authoritative merge signal — never compare…
Create a versioned GitHub release — detect the current version, bump by semver, update version manifest files, commit, tag, push, and run gh release create with auto-generated notes. Use ONLY when the user explicitly types /github-dev:release or asks to cut, publish, or tag a release. Do NOT auto-fire from incidental…
Resolve a GitHub issue end-to-end — analyze the issue, create a feature branch, implement the fix (TDD when the issue is marked), run verification gates, open a PR, and drive the cr-fix review loop to convergence. Use ONLY when the user explicitly types /github-dev:resolve-issue or asks to resolve or implement a…
Use to read or update .claude/state/spec.json — the aggregate cache of spec file → linked issue/PR → core description for in-flight and completed work. Single-file entry point for "what's in progress?" at session start. Triggers — "state 갱신", "spec/issue/PR 진행", "what's in flight", "state update".
Sync project progress to GitHub milestones and issues — recompute module progress, regenerate the milestone table and Type M-2 architecture diagrams, and update the tracked sections in issue and milestone bodies. Use when the user types /github-dev:update-progress, says "update progress", or asks to sync milestone or…
Karpathy LLM-Wiki 3-layer (insight + wiki + raw under neutral .llmwiki/): 5 skills (query/ingest/lint/bootstrap/migrate) + 5 hooks + bootstrap templates. Three soft hints plus an auto-capture/ingest path: a Stop hook mechanically captures ingest candidates to /.staging/ and the next session's SessionStart drain h.
Use to scaffold the LLM-Wiki knowledge system (.llmwiki/ insight + wiki + raw, plus spec) in a new repo that doesn't have it yet. Copies templates from the plugin's bundled assets, prompts for project pitch and 1-3 first domains, writes a slim CLAUDE.md.
Use after producing a new audit md, after merging a PR with non-obvious findings, or when a debugging session uncovers lore worth saving. Pulls the finding into the wiki with reversible diff-log + multi-page cross-update. Universal — works in any repo with a .llmwiki/wiki/ or legacy .claude/wiki/.
Use when the user asks to audit wiki health, or periodically (manual trigger) to catch the 4 wiki-rot failure modes — identity duplication, level flattening, monotonic relationships, and staleness. Universal — works in any repo with a .llmwiki/wiki/ or legacy .claude/wiki/.