apply-all-findings

Implements every code review finding or creates GitHub tracking issues for deferred items.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill apply-all-findings-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-all-findings
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/apply-all-findings
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill apply-all-findings-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often produce findings that get silently dropped, letting minor issues accumulate into technical debt. This Skill enforces a strict rule: every review finding is either fixed and verified, or deferred with a GitHub tracking issue linked in the review artifact. ## Core Features & Use Cases - Systematic Finding Resolution: Converts every review finding into a checklist item and works through fixes for critical, major, and minor issues (naming, documentation, style). - Enforced Deferral Tracking: Any finding not fixed in the current PR must produce a GitHub issue via gh issue create with labels like review-finding and spawned-from:#PR, linked back in the review artifact. - Verification Gate: Re-runs lint, typecheck, tests, and build, then updates the review artifact to confirm "Unaddressed: 0" before completion. - Use Case: After a comprehensive review of PR #123 lists five findings, use this Skill to fix three in place, create tracking issues for two out-of-scope items, and update the review comment so nothing disappears without a trace. ## Quick Start Apply all findings from the latest code review, fixing what you can and creating GitHub tracking issues for anything deferred.

Frequently Asked Questions about apply-all-findings

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

FAQPage Schema
How do I handle all code review findings systematically?

Convert every finding into a checklist item, then fix each one and verify, or defer it with a GitHub tracking issue. The rule is that every finding ends as FIXED or DEFERRED with a linked issue, never unaddressed.

How do I create a GitHub tracking issue for a deferred review finding?

Use gh issue create with a title referencing the finding and source PR, plus labels like review-finding and spawned-from:#PR. Then link the new issue number in the review artifact so the deferral is traceable.

When is it acceptable to defer a code review finding?

Deferral is valid only for out-of-scope architectural changes, external dependencies, breaking changes, or genuinely separate concerns. Reasons like "it's minor" or "takes too long" are rejected, and every deferral requires a tracking issue.

What checks should run after fixing review findings?

Re-run linting, type checking, tests, and the build, then review the git diff for unrelated changes. Finally update the review artifact marking findings as fixed or deferred and confirm "Unaddressed: 0".

Can minor review findings be skipped without tracking?

No. The skill explicitly forbids dropping minor findings without a trace because they compound into technical debt. Each minor finding must be fixed immediately or tracked in a GitHub issue linked from the review.