Sweepi Skill

AGENTS.md

SKILL.md

AGENTS.md

AGENTS.md

When to run

1. The user explicitly asks to run

   sweepi

   .
2. You are about to commit or recommend committing code changes.
3. You are linting code, or the user asks you to lint code.

Required workflow

1. Run Sweepi in this order:
   • First try global CLI:

     sweepi .

   • If

     sweepi

     is not found, fallback to:

     npx sweepi .

2. Parse all reported issues.
3. Follow the hard-gate pre-edit process in local

   AGENTS.md

   .
4. For each rule violation, open the rule docs in:

   • https://raw.githubusercontent.com/jjenzz/sweepi/main/packages/eslint-plugin-sweepit/docs/rules/<rule-id>.md

5. Apply fixes that match the documented intent, not only a minimal syntax pass.
6. Re-run

   sweepi

   until issues are resolved (or document blockers if resolution is impossible).

Resolution guidance

• Preserve the documented architectural constraints (compound parts, event-driven APIs, explicit props, etc.).
• Prefer changes that align with the rule's reasoning section.
• If a fix has trade-offs, choose the option that best matches the rule docs and explain the choice.
• Never trade behavior-preserving architecture for a smaller lint-only diff.
• Do not suppress or ignore rules by default.
• A rule may be ignored only when a human-in-the-loop (HITL) explicitly authorizes that specific exception.

Response format

1. The command you ran.
2. Which rules were triggered.
3. Rule analysis and fix mapping required by

   AGENTS.md

   .
4. The final Sweepi result (clean or remaining blockers).