remediation-loop
Structured remediation loop for code review findings. After a reviewer agent returns HIGH+ severity findings, dispatch a targeted fix agent, then re-review. Bounded to 2 cycles to prevent infinite loops. Use when code review or verification surfaces issues that need fixing before completion.
What this skill does
# Remediation Loop
When a code review or verification step surfaces findings with severity >= HIGH, run a bounded fix-then-re-review cycle instead of leaving the findings unresolved or asking the user to fix manually.
## When to Use
- A code-reviewer agent returned HIGH or CRITICAL findings
- A verification step found failing tests or integration issues
- A silent-failure scan identified error-handling gaps
- Any quality gate failed with actionable findings
## Protocol
### Step 1 — Assess Findings
Classify each finding:
- **Actionable**: has a clear fix (wrong logic, missing check, broken import)
- **Judgment call**: requires user input (architecture change, scope decision)
If ALL findings are judgment calls, present them to the user. Do not enter remediation.
### Step 2 — Fix (Bounded)
Dispatch a fix agent (or fix directly) scoped to ONLY the actionable findings:
```
Agent: Fix the following review findings. Do not refactor beyond what is needed.
Findings:
1. [file:line] — description from reviewer
2. [file:line] — description from reviewer
Constraints:
- Fix only what is listed. No drive-by improvements.
- Run existing tests after fixing to verify no regressions.
- Report what you changed and test results.
```
### Step 3 — Re-Review
After the fix, dispatch a fresh reviewer (or re-run verification) scoped to the same areas:
```
Agent (read-only): Review ONLY the files touched by the fix.
Confirm whether each original finding is resolved.
Report any new issues introduced by the fix.
```
### Step 4 — Decide
| Re-review result | Action |
|-----------------|--------|
| All findings resolved, no new issues | Exit loop — mark complete |
| New issues found (cycle 1) | Run one more fix + re-review cycle (Step 2-3) |
| New issues found (cycle 2) | **Stop.** Present remaining issues to user. Do not loop further. |
| Original findings NOT resolved | **Stop.** Present to user with evidence of what was tried. |
### Hard Limits
- **Maximum 2 remediation cycles.** Never exceed this. If 2 cycles don't resolve it, the user needs to decide.
- **No scope creep.** Each fix agent is scoped to specific findings. Do not expand scope across cycles.
- **Track what was tried.** When presenting remaining issues to the user, include: original finding, what fix was attempted, why it didn't resolve.
## Anti-Patterns
- Running remediation on LOW/INFO findings (not worth the cost)
- Expanding fix scope beyond the original findings
- Looping more than twice ("if 2 passes didn't fix it, a 3rd won't either")
- Remediating judgment calls without user input
- Skipping the re-review step ("I'm sure the fix is correct")
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.