robust-fix

Automatically fix S-Critical and S-High findings from robust-review with verification gates.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nok0321/claude-pipeline --skill robust-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: robust-fix
Source: https://github.com/nok0321/claude-pipeline/tree/main/skills/robust-fix
Command: npx skills add https://github.com/nok0321/claude-pipeline --skill robust-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically fixes S-Critical and S-High findings detected by robust-review, applying standardized remediation patterns and ensuring safety through automated verification gates (build, type checks, and tests) before release.

Core Features & Use Cases

  • Automated remediation: applies predefined, safe patches for critical findings.
  • Verification-driven: executes build/type/test gates after each fix to ensure stability.
  • Escalation routing: directs nontrivial design decisions to Tier 1 or other skills like spec-fix if needed for policy alignment.

Quick Start

Run /robust-fix immediately after a robust-review finding to automatically repair the latest issues and verify them through the gates.

Frequently Asked Questions about robust-fix

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

FAQPage Schema
How do I automatically fix critical code findings after a review?

To automatically fix critical code findings, you can use an automated remediation tool that applies predefined patches to S-Critical and S-High issues. It enforces standard templates and verifies stability through build, type, and test gates before release.

Can I verify code fixes through build and test gates before release?

Yes, verifying code fixes through build and test gates before release is essential for stability. Automated remediation tools execute these verification gates immediately after applying patches to ensure the changes do not break existing functionality.

What is the best way to handle nontrivial design decisions during automated code remediation?

The best way to handle nontrivial design decisions during automated code remediation is through escalation routing. Complex issues are directed to Tier 1 support or specialized skills like spec-fix to ensure proper policy alignment.

Does automated remediation support dry-run mode for applying code patches?

Yes, automated remediation supports dry-run mode for applying code patches. This allows you to preview the standardized remediation patterns and evaluate the proposed changes before they are actually executed on your codebase.

How do I batch process Tier 2 findings in my codebase?

To batch process Tier 2 findings in your codebase, apply an automated remediation tool to handle multiple issues at once. It integrates with verification gates and routes complex nontrivial design decisions to escalation if required.

When should I escalate code fixes instead of using automated remediation?

You should escalate code fixes instead of using automated remediation when the issues involve nontrivial design decisions. Routing these complex cases to Tier 1 or other skills ensures proper policy alignment that standard templates cannot handle.