メニュー
Revise an existing file as discrete reviewable hunks, never a wholesale overwrite. USE WHEN editing, rewriting, or revising a document, note, config, or file the user will review, especially one they have already hand-edited.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and validate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions.
Create, validate, evaluate, and iterate skills for forge modules. USE WHEN create skill, new skill, write skill, validate skill, check skill, skill structure, skill conventions, test a skill, run skill evals, benchmark a skill, skill not triggering, optimize skill description. Not for adopting community skills (AdoptArtifact) or shipping artifacts downstream (PublishArtifact).
Create, validate, or place behavioral rules in forge modules. USE WHEN create rule, new rule, write rule, capture rule, add a rule, graduate a correction or convention to a rule, validate rule, rule conventions, where does this rule belong, or the user runs /Rule.
Scaffold a workshop project: a VCS spine (git + jj colocate + entire + forge hooks), the private/public/assets flow layout with a .tlp manifest, a .claude/ that mounts the knowledge vault, and on-demand satellites (vault folder-note, data dir, private remote). USE WHEN starting a new project, initializing a folder for work, adding a vault note or data dir or remote to a project, archiving a project, or the user runs `project` / `atlas`.
Collaborative ideation before implementation — explore context, clarify intent, propose approaches. USE WHEN starting creative work, new features, design decisions, or modifying behavior.
Write a formal design spec from brainstorming output or requirements. USE WHEN design approved, write spec, formalize design, spec document.
| name | IncrementalEdits |
| description | Revise an existing file as discrete reviewable hunks, never a wholesale overwrite. USE WHEN editing, rewriting, or revising a document, note, config, or file the user will review, especially one they have already hand-edited. |
| version | 0.1.0 |
When you revise a file the user will review, change it hunk by hunk with targeted edits, one concern per edit. A single write that replaces the whole file is the wrong tool whenever discrete edits would do.
| Thought | Reality |
|---|---|
| "I'll just rewrite the whole file, it's cleaner" | The reviewer loses the diff and their own edits. Edit the spans that move. |
| "The content is pre-approved, a full write is fine" | Approval is about content, not delivery. Land it as hunks anyway. |
| "Many small edits are noisy" | Small edits are the review surface. One concern per edit beats one blob. |
