Skip to content
cccskills
FreePublished on GitHub

check-pr

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.

Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Check PR for Coding Rule Compliance

Checks compliance with atomic project rules (memory/code/, memory/architecture/) and hard-reject rules in docs/architecture/code-review-rules.md. Not a general code review.

$ARGUMENTS: PR number, PR <number>, or full GitHub URL.

Steps

1. Load rules

  • memory/INDEX.md — scan, then read each relevant atom under memory/code/ and memory/architecture/
  • docs/architecture/code-review-rules.md — hard reject rules
  • docs/architecture/design-rules.md — reference when an atom cites a §-section

2. Fetch the PR

gh pr diff <number> --repo <repo>
gh pr view <number> --repo <repo> --json title,body,files

3. Check each changed file

memory/ atoms — scan memory/INDEX.md and read every atom whose trigger matches a changed file (read the atom before flagging). The INDEX is the source of truth; an inline copy here would drift as atoms are added or renamed.

code-review-rules.md:

  • disabled="@boolValue" Razor boolean attribute traps
  • Missing [Authorize] or [ValidateAntiForgeryToken] on POST actions
  • Missing .Include() for navigation property access
  • Silent exception swallowing (catch without logging)
  • Orphaned pages (new action with no nav link)
  • Cache mutations without eviction
  • Form field preservation on validation failure
  • Renamed [JsonPropertyName] attributes
  • HasDefaultValue(false) on bools
  • Batch methods missing single-item guards
  • Inline onclick/onsubmit handlers (CSP violation)
  • Dead code

4. Report

Before reporting a violation, read the actual file at those lines — do not flag from diff context alone.

Output per violation: Rule (atom path or rule name), File (path:line), Code (snippet), Fix. List clean files under ### CLEAN. End with files checked, violations found, and severity:

  • BLOCK — any code-review-rules.md hard-reject violated
  • WARN — only memory/ atom violations
  • CLEAN — no violations

Do NOT make code changes.

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

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

finish

Free

End-of-session cleanup for coding and project work. Use when the user says "finish", "wrap up", "done for now", or any variation of ending a work session.

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