Skip to content
cccskills
FreePublished on GitHub

reuse-review

Review a local diff or PR for unnecessary durable surface: new files, public types, interface methods, DTOs/view models, helpers, routes, DI registrations, services, repositories, and dependencies that should reuse existing owners instead.

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

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reuse Review

This is not a correctness review. It checks whether the change added durable surface where reuse, caller-side composition, or an existing owner would have been better.

Inputs

$ARGUMENTS can be:

  • PR <number> - review an existing PR on peterdrier/Humans
  • Empty - review the current branch against origin/main

Steps

  1. Read:
    • CLAUDE.md reuse-first section
    • memory/process/reuse-first-change-discipline.md
    • memory/architecture/interface-method-additions-are-debt.md
    • docs/architecture/reuse-review-rules.md
  2. Fetch the diff:
    • PR: gh pr diff <number> --repo peterdrier/Humans
    • Local: git diff --find-renames origin/main...HEAD
  3. Build a surface inventory:
    • new files
    • new public types
    • interface method changes
    • new/changed service and repository methods
    • new DTOs/view models/helpers
    • new controller actions/routes/pages
    • new DI registrations and package references
  4. For each item, search for the existing owner/surface before flagging.
  5. Report only concrete findings. A finding must name both the new surface and the existing surface that should absorb or replace it.

Output

Use this format:

## Reuse Review: PASS|WARN

### Findings
- REUSE - <new surface> should reuse <existing surface>.
  Why: <cost/risk>.
  Fix: <specific consolidation or caller-side composition>.

### Surface Inventory
- New files:
- Public/interface surface:
- Services/repositories:
- DTOs/view models/helpers:
- Routes/pages:
- DI/dependencies:

If there are no findings, say PASS - no unnecessary durable surface found and still include the surface inventory.

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