Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From code-habits
Use when about to mark a task as complete, done, finished, or shipped — verifies the deliverable actually exists as a file on disk, in a commit, or as a posted artefact. Blocks claiming completion based on chat output alone.
npx claudepluginhub amitkot/claude-code-tools --plugin code-habitsHow this skill is triggered — by the user, by Claude, or both
Slash command
/code-habits:deliverable-on-diskThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Don't mark a task done when the only evidence is what you said in chat. The deliverable has to actually exist: file written, commit made, PR opened, plan saved.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Don't mark a task done when the only evidence is what you said in chat. The deliverable has to actually exist: file written, commit made, PR opened, plan saved.
Chat output is ephemeral and not the artefact. If a user comes back later expecting "the plan we wrote" or "the script we built", they need it on disk. "I described the plan in the conversation" doesn't survive a new session, a teammate's review, or a context rotation.
Before declaring a task complete, verify the artefact exists where the user expects it:
docs/plans/<slug>.md).git diff shows the change.gh pr view returns it.If the deliverable IS "an answer in chat" (a question), then chat output is the deliverable and this skill doesn't apply. Otherwise, verify the artefact exists before claiming completion.