Confirm gate
Skills for any AI agent harness, by Mad House
npx -y skills add samhcus/skills --skill confirm-gateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Surface your interpretation of the task before writing any code or making any changes. Use this at the START of any Build mode task - before opening a single file to edit. Critical when the request contained multiple ideas, was written in fragments, affects more than 2 files, or has any ambiguity about scope. Triggers on "build", "create", "add", "implement", "write", "make", "fix", "update" when the request is non-trivial. Do not skip this step to save time - a wrong interpretation wastes more time than a confirmation.
SKILL.md
1.4 KB, as published. Nobody here has run it
Confirm Gate
Before touching anything, surface your interpretation. Output exactly this structure and stop:
Mode: [Plan / Build / Debug / Review - pick one]
I'm reading this as: [one sentence - what you think the actual task is, stripped of noise]
I'll touch:
- [specific file or component]
- [specific file or component]
I won't touch: [anything explicitly out of scope, or "nothing excluded" if full scope]
First step after confirmation: [the single next action]
Ambiguities: [anything unclear that would change the plan - or "none"]
Then stop. Do not proceed until the user responds.
If the user confirms ("yes", "go", "proceed", "looks right") - execute. If the user corrects anything - update your interpretation and confirm again before proceeding. If the user says "just do it" - execute but note what assumption you made.