Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-status
A read-only summary of .codearbiter/ state. No skill is routed to; no file is modified.
The orchestrator reads and presents:
stage: maturity value from <project-root>/.codearbiter/CONTEXT.md frontmatter.<project-root>/.codearbiter/specs/ and plans/, with howfar each got: spec awaiting approval, spec approved / no plan, plan in progress (ACCEPTED count
vs. total from the plan's status column), or complete. An interrupted pipeline is resumable via
/ca-feature — say so on its line.
<project-root>/.codearbiter/open-tasks.md(top-level - bullets excluding done - [x]; the same _taskboardlib count the
SessionStart hook uses).
[CONFIRM-NN] placeholders in<project-root>/.codearbiter/open-questions.md.
<project-root>/.codearbiter/overrides.lognewer than the marker in <project-root>/.codearbiter/last-checkpoint.
## Project status — YYYY-MM-DD
Stage: N
Branch: <current branch>
Pipelines:
<slug> plan 3/7 ACCEPTED — resume with /ca-feature "<slug>"
<slug> spec approved, no plan
Open tasks: N
Open questions: N ([CONFIRM-NN] unresolved)
Overrides since last checkpoint: N
No specs and no plans → Pipelines: none.
If [CONFIRM-NN] placeholders are open, surface them — do not resolve them here.
/ca-checkpoint./ca-btw.Read-only. MUST NOT modify any file. MUST NOT resolve a [CONFIRM-NN] it surfaces. No skill is routed
to by this command.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take arbiterforge/codearbiter-ca-status from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.