MartinoPolo/mp-fallow-fix
skills/mp-fallow-fix/SKILL.md
Diagnose and fix fallow dead-code or audit failures. Use when: fallow check fails, dead-code regression detected, unused exports/types found, or agent needs to suppress/baseline fallow findings. Also use when working with code quality suppressions (@public, fallow-ignore).
$ install --global
skillsauthnpx skillsauth add MartinoPolo/mpx-claude-code mp-fallow-fixInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 6:54 AM113.9s1 file scanned
SKILL.md
- name:
- mp-fallow-fix
- description:
- Diagnose and fix fallow dead-code or audit failures. Use when: fallow check fails, dead-code regression detected, unused exports/types found, or agent needs to suppress/baseline fallow findings. Also use when working with code quality suppressions (@public, fallow-ignore).
- allowed-tools:
- Read, Edit, Glob, Grep, Bash(*fallow*), Bash(pnpm *fallow*), Bash(git diff*), Bash(git log*)
- author:
- MartinoPolo
- version:
- 0.1
- category:
- code-quality
Fallow Fix
Diagnose and resolve fallow code-quality failures. $ARGUMENTS
Step 1: Identify the Failure
Run the appropriate diagnostic command based on what failed:
- Dead-code regression (
check:fallowfailed): output already shows all issues with file:line and rule explanations - Audit failure (fallow-gate hook blocked commit/push):
pnpm fallow:auditfor JSON details - Need more detail: re-run
pnpm check:fallow—--explainincludes rule descriptions and docs URLs
Parse the JSON output. Each issue has path, line, name, severity, and actions.
Step 2: Categorize Each Issue
For each issue, determine the correct action:
Fix (default — remove the dead code)
- Unused file → delete it
- Unused export → remove the
exportkeyword or delete the declaration - Unused dependency →
pnpm remove <package> - Stale suppression → remove the
// fallow-ignore-*comment
Suppress (only when the code is intentionally unused)
| Situation | Suppression |
| ------------------------------------------------- | ---------------------------------------------------------------------------- |
| Public API export consumed by external packages | /** @public */ above the export |
| Intentionally pre-exported for planned use | /** @expected-unused */ above the export (becomes stale warning when used) |
| Framework lifecycle method (mount, destroy, etc.) | // fallow-ignore-next-line unused-class-member |
| Interface implementation method | // fallow-ignore-next-line unused-class-member |
| High-complexity function that can't be split now | // fallow-ignore-next-line complexity |
| Entire generated file | // fallow-ignore-file at top |
Never use blanket // fallow-ignore-next-line without specifying the kind.
Available suppression kinds
unused-export, unused-type, unused-class-member, unused-enum-member, unresolved-import, unlisted-dependency, duplicate-export, circular-dependency, complexity, code-duplication, coverage-gaps
Step 3: Apply Fixes
- Fix or suppress each issue
- Re-run the failing command to verify
- If dead-code count legitimately changed (new public API, refactored exports): update the baseline
pnpm fallow:save-baseline
Commit the updated fallow-baselines/dead-code-regression.json alongside your code changes.
Step 4: Verify
Re-run the original failing check:
pnpm check:fallow— must exit 0pnpm fallow:audit— verdict must bepassorwarn
Rules
- Prefer removing dead code over suppressing it
- Every suppression must have a clear reason (public API, framework requirement, etc.)
- Never suppress to make checks pass without understanding why the code is unused
- Always commit baseline updates in the same PR as the code changes that caused them
stale-suppressionsis set toerror— orphaned suppression comments will fail checks
Related Skills
MartinoPolo/mp-skill-audit
development
VerifiedTrustedCommunity
Audit all active skills for consistency, convention drift, and common issues. Auto-fixes where possible, reports remaining issues. Use when: "audit skills", "skill audit", "check skills", "lint skills"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-ship
testing
VerifiedTrustedCommunity
Ship finished work: sync base, commit, push, PR, wait for CI green, merge. Use when: "ship it", "ship and merge", "ship this"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-harvest-decisions
development
VerifiedTrustedCommunity
Scan recent Claude Code sessions for grilling/design discussions, extract decisions, and update CONTEXT.md + DECISIONS.md. Use when: "harvest decisions", "extract decisions from sessions", "update docs from sessions", "sync decisions"
1SKILL.mdUpdated May 19, 2026
MartinoPolo/mp-consolidate-context
tools
VerifiedTrustedCommunity
Consolidate CONTEXT.md: remove duplicates, outdated items, tighten language. Use when: "consolidate context", "clean up context", "simplify context", "consolidate requirements"
1SKILL.mdUpdated May 19, 2026