Skip to content
cccskills
FreePublished on GitHub

spec-review

Review code changes against linked GitHub issue specs to catch implementation drift — building something plausible but wrong. Checks each acceptance criterion against actual code.

The English summary is being prepared. Showing the original description.

Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Spec Compliance Review

Review whether the code changes actually implement what the linked GitHub issues specify. This is NOT a code quality review — it answers "did you build the right thing?"

Follow the full process documented in .claude/agents/spec-compliance-reviewer.md.

Input

$ARGUMENTS can be:

  • PR <number> — review an existing PR on peterdrier/Humans
  • owner#NNN owner#NNN ... — review current changes against specific issues; the repo qualifier is required (peterdrier#NNN or nobodies-collective#NNN). If a ref is unqualified, stop and ask which repo — never guess.
  • Empty — scan recent commit messages for issue references and review against those

Execution

  1. Identify issues (from PR body, arguments, or commit messages)
  2. Fetch each issue from its home repo via gh issue view <number> --repo <owner>/Humans — resolve the owner from the qualified ref per memory/process/issue-refs-qualified.md. An unqualified ref is an input error: stop and ask, never guess
  3. Extract all acceptance criteria and behavioral requirements from each issue
  4. Read the actual code changes (PR diff or local diff)
  5. For each criterion, check the CODE (not the PR description) — quote evidence for PASS, explain divergence for FAIL
  6. Detect systemic drift (wrong data source, wrong audience, missing conditional branches)
  7. Produce the structured report from the agent doc

After Review

Present the report. Do NOT make any code changes. If there are BLOCKING issues, clearly state what needs to change before the PR can merge.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Check an externally created PR for coding rule violations against memory/INDEX.md atoms and docs/architecture/code-review-rules.md.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

Review, repair and steward the nightly Codex debt-sweep PR (branch codex/daily-debt/<date>). Judges every commit GOOD / REPAIR / REVERT, triages the bot review findings through /fix, lands one round-1 commit, files follow-up issues, then stewards the PR itself with a 3-round ceiling. Run by the 08:00 UTC cloud routine; also '/debt-review', '/debt-review 1789'.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

Scrap and regenerate the in-flight EF migrations on the current branch as one consolidated migration. Use when migrations have accumulated mid-development cruft (added/removed columns, stacked add-column-to-existing-table fixes, hand-edited SQL that needs to come out, schema changes that should have been one migration but ended up as five), or when the branch has merged main and its migrations are now stuck mid-chain so `dotnet ef migrations remove` is unsafe. Triggers on phrases like 'regen the migrations', 'redo these migrations', 'scrap and regen migrations', 'consolidate the in-flight migrations', 'redo the migration stack', or any time an agent hits the mid-chain situation in `memory/architecture/migration-regen-after-rebase.md`.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

Use when a sprint tracking issue (label `sprint`) on peterdrier/Humans needs working — routine-fired cloud runs, or any unattended session told to execute the sprint queue.

The English summary is being prepared. Showing the original description.

nobodies-collective/Humans4Updated Oct 22, 2026

See all skills by nobodies-collective

Report a problem with this skill