girishr

Specpilot Sync — Development skill for Claude Code

Development community

Compare .specs/ against actual project state and propose fixes for drift.

How to install Specpilot Sync

Installs to ~/.claude/commands/girishr-specpilot-specpilot-sync.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/girishr/SpecPilot/HEAD/.claude/commands/specpilot-sync.md -o ~/.claude/commands/girishr-specpilot-specpilot-sync.md

Restart Claude Code, or start a new session, for it to be picked up.

What Specpilot Sync does

description: Compare .specs/ against actual project state and propose fixes for drift

Find and fix drift between `.specs/` and the real project.

Read .specs/architecture/architecture.md, .specs/project/requirements.md, and .specs/quality/tests.md.
Compare their claims against the actual src/ structure and package.json (versions, dependencies, scripts).
List concrete discrepancies: stale version numbers, renamed or removed files/modules still referenced, undocumented

Alternatives in Development

Epic Claim — Claim an epic issue, stamp coordination state, and sync local ownership 243.5k ★
Purpose — Orient yourself in pi-vs-cc — a collection of Pi coding agent extensions and agent specs that progressively de 527 ★
Overnight PRs — Autonomous overnight loop — verify issues against the codebase, close stale ones, ship PRs through /ship (bug 324 ★