# Reject

> 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.

- Skill: `foliveira/reject` (Agent Skill)
- Install (CLI): `npx skillmds@latest add foliveira/reject`
- Raw SKILL.md: https://api.skillmd.com/api/skills/foliveira/reject/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: foliveira (https://skillmd.com/u/foliveira)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/foliveira/reject

---


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
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.