skills.rest
Mozurok
MozurokCOMMUNITY
Explore all skills by this author →
GitHub

apply-sweep-triage

Persist sweep triage decisions into REVIEW_PREFERENCES.md for future finding suppression.

6|Updated Jul 10, 2026
Search Tags:#git#workflow#code review#triage#sweep#suppression#task state
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill apply-sweep-triage-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apply-sweep-triage
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/apply-sweep-triage
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill apply-sweep-triage-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a repository consistency sweep produces findings, triage decisions made in chat are lost unless written to disk. This Skill persists the user's apply, decline, and discuss decisions from a SWEEP snapshot into REVIEW_PREFERENCES.md so future sweeps suppress declined findings and track applied fixes. ## Core Features & Use Cases - Triage persistence: Reads triage values (apply, decline, discuss) from a SWEEP snapshot and appends them to the corresponding tables in REVIEW_PREFERENCES.md. - Suppression anchoring: Computes git file hashes for declined findings so suppression entries age out when the underlying file changes. - Deduplication: Updates existing rows keyed by bug class and file path instead of appending duplicates, and updates TASK_STATE.md with a triage summary. - Use Case: After running repo-consistency-sweep and marking each finding as apply, decline, or discuss in the snapshot, run this Skill to record those decisions permanently so the next sweep does not re-report declined items. ## Quick Start Persist the triage decisions I marked in the latest SWEEP snapshot into REVIEW_PREFERENCES.md and update the task state.

Frequently Asked Questions about apply-sweep-triage

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

FAQPage Schema
How do I persist sweep triage decisions so future sweeps ignore them?▼

Mark each finding in the SWEEP snapshot with a triage value of apply, decline, or discuss, then run this Skill. It writes the decisions into REVIEW_PREFERENCES.md, and future repo-consistency-sweep runs suppress declined findings.

How does declined finding suppression work across file changes?▼

Each declined row stores a git file hash captured with git hash-object at triage time. When the file changes, the hash no longer matches and the declined entry ages out, so the finding can resurface.

What happens if some findings have no triage value set?▼

Findings with triage unset are skipped because the user has not decided yet. If every finding is unset, the Skill returns a no-op and persists nothing.

Does this Skill modify the SWEEP snapshot or fix the code?▼

No. The SWEEP snapshot is treated as a read-only historical record, and the Skill performs persistence only. It never implements code fixes; it only records decisions and updates TASK_STATE.md.

What happens when the same finding is triaged twice?▼

The Skill deduplicates by bug class plus file path. If an identical row already exists in the target table, it updates the existing row's date, file hash, and reason instead of appending a duplicate.

Related Skills

Explore More Software Engineering Skills→
JennyfirrrJennyfirrr

bug-check

Scan codebases for known bug classes and report per-class verdicts with citations.

Community
Advanced
flosrnflosrn

refactor

Refactor code across a codebase using parallel agents and validation.

Community
Advanced
ActiveMemoryActiveMemory
74

ctx-add-decision

Record architectural decisions in DECISIONS.md with context, alternatives, rationale, and consequences.

Official
Intermediate
RideMatch1RideMatch1

ops-triage-aegis-finding

Standardize severity, verification, and routing decisions for AEGIS findings.

Community
Advanced