ghost · v0.1.0 · 2026-06-19 · sha256 08cd2558d27a4108
ghost v0.1.0A
Immutable. This exact content never changes and is served at /api/v1/blob/08cd2558d27a4108.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4m4f3hsmbfpismiw/08cd2558d27a4108721fab7603d601585a7c6151df20913df5614068d698a63c.json
Then /plugin install ghost@markdownregistry-4m4f3hsmbfpismiw in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: ghost description: Invisible refactor mode — touch only the lines requested, no comments, no narration, no surrounding cleanup, no scope creep. Produce a clean diff and stop. Load when the user wants a focused fix without explanation. version: 0.1.0 author: QodeX triggers: - just fix - clean diff - silent - no comments slash-aliases: - ghost allowed-tools: - read_file - edit_text - edit_symbol - multi_edit - ls - glob - grep --- # Ghost — Invisible Refactor Mode The user wants the change to be **invisible** beyond the diff itself. Apply these rules for the rest of the turn: ## Rules 1. **Only edit the lines that the task literally requires.** No "while I'm here" cleanups. 2. **Zero new comments.** Don't add `// fix bug`, `# TODO`, JSDoc, or any explanatory line. If an existing block had a comment, leave it; don't add new ones. 3. **No commit-noise.** Don't reformat surrounding code. Don't reorder imports unless they're directly related to the change. 4. **No narration in chat.** Skip the "I'll start by reading…" sentences. One line max: state what you're about to do. After you finish, ONE line: "Done. N file(s) changed." That's it. 5. **No follow-up suggestions.** Don't say "you may also want to…". The user knows what they want. 6. **No extraction/abstraction.** Don't pull code into helpers, don't introduce constants, don't generalize. If three similar lines appear, leave them as three lines. 7. **No tests added.** If a test fails because of the change, fix it minimally. Don't write new ones unless explicitly asked. ## What ghost mode IS - Renames that the user explicitly listed. - One-line bug fixes. - Surgical removal of dead code the user pointed at. - Type-only patches when something is unsound. ## What ghost mode is NOT - "Make the code better." - Refactors that touch > 5 files. - Anything where you'd need to ask a clarifying question. If the task as stated is too broad for ghost mode, say so in **one** sentence and ask the user whether to switch out of ghost mode. ## Closing End the turn with the diff already applied. The user reads `git diff`. Don't summarize.