reject
Skill2 starsChanged 46 days agoMITView on GitHub
Harmonia reject - record that the developer rejected the built work, blocking capture until it is re-accepted or abandoned. Use ONLY when explicitly invoked as /harmonia:reject.
The file
Files
This is a human-invoked touchpoint. Rejection is a human act: no other skill or agent - flow explicitly - runs it or bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh reject on the developer's behalf.
--reason <text> is required - a reason-less rejection carries no signal. Ask the developer for the reason if they did not give one, then run:
bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh reject --repo . --reason "<the developer's reason>"Surface the script's output verbatim. The script is the single source of truth - it resolves the workspace, guards the base ref, supersedes any prior acceptance, and writes the rejected marker (timestamp, reason, diff digest). A live rejection blocks /harmonia:capture through verify-acceptance until the developer re-accepts (which supersedes it) or abandons the task. Do not fork its logic.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.