repo-consistency-sweep

Detects defect classes in task diffs against a curated bug-class library before PR packaging.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill repo-consistency-sweep-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-consistency-sweep
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/repo-consistency-sweep
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill repo-consistency-sweep-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review often burns human attention on low-value pattern checks (convention drift, ordering bugs, type-safety gaps) instead of design and intent. This Skill automates that lower-value half of review by sweeping the current task diff against a curated bug-class library, so reviewers only see triageable, severity-ranked findings before a PR is packaged. ## Core Features & Use Cases - Bug-class pattern detection: Loads bug-class templates from wos/bug-classes/, matches them to changed files, and produces findings with severity (P0/P1/P2), confidence, effort band, and suggested fixes. - Substrate audit: Runs header-drift, orphan-bullet, and verification-log validation scripts on task-memory files, surfacing counts as informational WARN signals. - Declined-finding suppression: Reads REVIEW_PREFERENCES.md to suppress findings the user previously declined, until the underlying file changes. - Use Case: After implementing a slice and running a design review, invoke the sweep to catch a missed multi-tenant invariant and an ordering bug in the diff, write a REVIEW_SWEEPS/SWEEP_<ts>.md snapshot, then route to PR packaging with reviewer attention points. ## Quick Start Run the repo-consistency-sweep on my current task diff to catch defect-class issues before I package the PR.

Frequently Asked Questions about repo-consistency-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a proactive code review sweep before packaging a PR?▼

Run the sweep after at least one slice is implemented and design review is done. It computes the diff against the base branch from SOURCE_OF_TRUTH.md, applies matching bug-class templates, and writes a findings snapshot under REVIEW_SWEEPS/ before routing to PR packaging.

What kinds of bugs does a bug-class library detect in a diff?▼

It detects convention drift, ordering bugs, type-safety gaps, security and multi-tenant invariants grounded in CWE categories, and operability issues. Each class defines file patterns, an analysis prompt, and severity and confidence rubrics.

Can I suppress findings I already declined in code review?▼

Yes. Declined findings are recorded in REVIEW_PREFERENCES.md with the file hash. The sweep suppresses a matching finding only while the file is unchanged; once the file is modified, the decline goes stale and the finding is reported again.

When should I not run a consistency sweep on my repository?▼

Skip it when no implementation has happened yet or the task is still in planning, since there is no diff to analyze. For design and intent review rather than defect-pattern detection, use a design-focused review pass instead.

Does the sweep fix the findings it reports?▼

No. It analyzes and reports only, producing findings with suggested fixes and triage placeholders. Fixes are applied separately, and P0 findings route the workflow back to implementation rather than to PR packaging.