7ffbb1f757
- CLAUDE.md with collaboration rules and Planner/Generator/Evaluator cycle - .claude/ agents, commands, skills, hooks per Claude Code conventions - Sprint Contracts for sut-prober, normalizer, recorder, player, diff-reporter - SUT catalog (EG-BIM Modeler, 187 plugins) and .gitignore excluding SUT tree - PROGRESS.md / PLAN.md as shared agent handoff state - Solution scaffold targeting sut-prober PoC Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
22 lines
883 B
Markdown
22 lines
883 B
Markdown
---
|
|
name: approve
|
|
description: Promote a received baseline to approved after human confirmation. Usage /approve <scenario-name>
|
|
allowed-tools: Read, Bash, Write, Glob
|
|
---
|
|
|
|
Promote a received golden file to an approved baseline.
|
|
|
|
Scenario name: `$ARGUMENTS`
|
|
|
|
Steps:
|
|
|
|
1. Refuse if `$ARGUMENTS` is empty. Ask the user for a scenario name.
|
|
2. Locate `baselines/$ARGUMENTS.received.*` files. Refuse if none exist.
|
|
3. Show the diff against the existing `*.approved.*` (if any) so the user can confirm the intent.
|
|
4. **Ask the user to type an approval reason** (intentional change / bug fix / new feature etc.). Record it.
|
|
5. Copy `*.received.*` → `*.approved.*`.
|
|
6. Write an entry to `docs/history/YYYY-MM-DD_approve-$ARGUMENTS.md` with the reason, diff summary, context usage, and duration.
|
|
7. Update `PROGRESS.md` baseline log.
|
|
|
|
Never approve without an explicit reason from the user.
|