/apply
Implement an approved OpenSpec change and keep tasks in sync.
$ npx -y skills add spencermarx/open-code-review --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/apply
Context preview
What this command does when you run it.
Implement an approved OpenSpec change and keep tasks in sync.
Command definition
apply.mdname: OpenSpec: Apply description: Implement an approved OpenSpec change and keep tasks in sync. category: OpenSpec tags: [openspec, apply]
<!-- OPENSPEC:START --> **Guardrails**
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
**Steps** Track these steps as TODOs and complete them one by one. 1. Read `changes/<id>/proposal.md`, `design.md` (if present), and `tasks.md` to confirm scope and acceptance criteria. 2. Work through tasks sequentially, keeping edits minimal and focused on the requested change. 3. Confirm completion before updating statuses—make sure every item in `tasks.md` is finished. 4. Update the checklist after all work is done so each task is marked `- [x]` and reflects reality. 5. Reference `openspec list` or `openspec show <item>` when additional context is required.
**Reference**
- Use `openspec show <id> --json --deltas-only` if you need additional context from the proposal while implementing.
<!-- OPENSPEC:END -->
AI-powered multi-agent code review. Simulates a customizable team of Engineers performing code review with built-in discourse.
Repo: spencermarx/open-code-review
Other commands on open-code-review.
- /COMMAND_COMPLIANCE_REPORT
Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage of: - `mcp__claude-flow__*` tools (preferred) - `npx claude-flow` commands (as fallback) - No direct implementation calls
Open command - /bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
Open command - /performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.
Open command - /performance-report
Generate comprehensive performance reports for swarm operations.
Open command - /token-efficiency
Reduce token consumption while maintaining quality through intelligent coordination.
Open command - /token-usage
Analyze token usage patterns and optimize for efficiency.
Open command

