/new-skill
Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
$ npx -y skills add arbiterForge/codeArbiter --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
/new-skill
Context preview
What this command does when you run it.
Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
Command definition
new-skill.mddescription: Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
argument-hint: "<verb-noun skill name>"
{{CMD:new-skill}} — author a skill
The only permitted entry to creating a skill. Nothing is written until the gap is proven uncovered — skills are not created speculatively. Name the skill in verb-noun form (`"dependency-review"`), not as a description (`"the thing that checks packages"`).
Flow
Routes to the `skill-author` skill, which owns the work end to end through its five gated phases — gap evidence, scope, authoring, self-review against the v2 house style, and routing integration (the `INDEX.md` + routing-table entry that makes the new skill reachable). The phase definitions live in the skill; this command does not restate them. Nothing is authored until an existing skill or agent is proven not to cover the need; nothing ships until the new skill carries gated phases, hard rules, and its routing entry.
Routes to
`skill-author` (`{{PLUGIN_ROOT}}/skills/skill-author/SKILL.md`) — all five phases.
When NOT to use
- A one-time action → `{{CMD:feature}}` or a command definition.
- An existing skill nearly covers it → extend that skill via `{{CMD:feature}}`.
- "Do we even need a skill here?" → `{{CMD:btw}}`.
Hard gate
MUST prove the gap is real in Phase 1 before writing any skill content. MUST get user approval on the spec before authoring. MUST NOT create a skill that duplicates an existing skill's purpose — surface the overlap instead. Skill files live only under `{{PLUGIN_ROOT}}/skills/<name>/`.
Read more
description: Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it. argument-hint: "<verb-noun skill name>"
{{CMD:new-skill}} — author a skill
The only permitted entry to creating a skill. Nothing is written until the gap is proven uncovered — skills are not created speculatively. Name the skill in verb-noun form (`"dependency-review"`), not as a description (`"the thing that checks packages"`).
Flow
Routes to the `skill-author` skill, which owns the work end to end through its five gated phases — gap evidence, scope, authoring, self-review against the v2 house style, and routing integration (the `INDEX.md` + routing-table entry that makes the new skill reachable). The phase definitions live in the skill; this command does not restate them. Nothing is authored until an existing skill or agent is proven not to cover the need; nothing ships until the new skill carries gated phases, hard rules, and its routing entry.
Routes to
`skill-author` (`{{PLUGIN_ROOT}}/skills/skill-author/SKILL.md`) — all five phases.
When NOT to use
- A one-time action → `{{CMD:feature}}` or a command definition.
- An existing skill nearly covers it → extend that skill via `{{CMD:feature}}`.
- "Do we even need a skill here?" → `{{CMD:btw}}`.
Hard gate
MUST prove the gap is real in Phase 1 before writing any skill content. MUST get user approval on the spec before authoring. MUST NOT create a skill that duplicates an existing skill's purpose — surface the overlap instead. Skill files live only under `{{PLUGIN_ROOT}}/skills/<name>/`.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Other commands on codearbiter.
- /add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
Open command - /adr-status
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Open command - /adr
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Open command - /arbiter
Exit maintainer dev mode — restore orchestration, remove the dev marker, log the exit.
Open command - /audit
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
Open command - /btw
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
Open command