fix

Identify and fix reported issues using severity-based planning and type checks.

243|5|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/alamenai/terrae --skill fix-alamenai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/alamenai/terrae/tree/main/.claude/skills/fix
Command: npx skills add https://github.com/alamenai/terrae --skill fix-alamenai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to triage and resolve defects found in reviews or user reports. This Skill provides a repeatable, plan-driven workflow to identify issues, categorize by severity, and apply minimal, high-quality fixes to restore software health.

Core Features & Use Cases

  • Severity-based planning and prioritization of fixes
  • Minimal-change patch application to preserve intent
  • Clear fix summaries and post-fix verification to ensure stability

Quick Start

Describe the issues from the review or user report, then apply fixes in severity order starting with Critical.

Frequently Asked Questions about fix

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

FAQPage Schema
How do I systematically fix code review issues and prioritize bug reports?

To fix code review issues systematically, you categorize defects by severity and apply minimal-change patches in a plan-driven workflow. This approach prioritizes critical issues first, applies targeted fixes, and verifies stability through post-fix type checks.

What is the best way to apply minimal fixes without breaking existing code intent?

Applying minimal fixes preserves original code intent by changing only what is necessary to resolve the reported defect. This targeted patching approach maintains software reliability while ensuring the fix does not introduce unintended behavioral changes.

Does this issue tracking workflow support severity-based prioritization for user-reported defects?

Yes, severity-based planning is fully supported to triage user-reported defects. Issues are categorized by severity, allowing teams to prioritize critical fixes first and restore software health through a structured, plan-driven resolution workflow.

How do I verify code stability after applying patches to resolve reported issues?

To verify code stability after applying patches, you perform post-fix verification via type checks. This step ensures the minimal-change fixes resolve the reported issues without introducing new type errors or breaking existing functionality.

Can I use this plan-driven workflow for any software project with categorized defects?

Yes, you can use this plan-driven workflow for any software project where defects are categorized by severity. It systematically handles issue identification, severity-based planning, targeted fixes, and post-fix verification to improve overall code quality.

What is the stepwise process for resolving defects found during code reviews?

The stepwise process for resolving defects involves identifying issues from reviews, categorizing them by severity, applying minimal-change fixes in priority order, and running post-fix verification type checks to ensure software stability and reliability.