fix-issue

Select, patch, and validate a Linear issue fix with status updates.

6|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/opmau/claude-code-framework --skill fix-issue-opmau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-issue
Source: https://github.com/opmau/claude-code-framework/tree/main/templates/.claude/skills/fix-issue
Command: npx skills add https://github.com/opmau/claude-code-framework --skill fix-issue-opmau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams address Linear issues by selecting the right bug, planning a focused patch, applying changes, verifying results, and updating the issue status.

Core Features & Use Cases

  • Select issues by ID or description to pinpoint the bug.
  • Plan and implement a minimal fix within 1-3 files, with guardrails to avoid scope creep.
  • Verify and close the issue by validating changes and updating Linear to Done with a concise summary.

Quick Start

Tell me to fix a Linear issue by providing its ID or a short description.

Frequently Asked Questions about fix-issue

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

FAQPage Schema
How do I fix a Linear bug end-to-end in a single session?

You can fix a Linear bug end-to-end by selecting the issue, planning a minimal patch within 1-3 files, verifying the changes, and updating the issue status to Done with a concise summary.

What is the best way to resolve a tracked Linear issue without scope creep?

The best way to resolve a tracked Linear issue without scope creep is to enforce guardrails that limit code changes to a small set of 1-3 files and restrict debugging to a maximum of two fix attempts.

Can I use a description instead of an ID to pinpoint a Linear bug for debugging?

Yes, you can select a Linear issue for debugging by providing either its specific ID or a short description to pinpoint the exact bug before planning your patch.

What steps are involved in patching and validating a Linear issue fix?

Patching and validating a Linear issue fix involves gathering evidence, planning the implementation, applying code changes, verifying the results, and recording the final outcome in Linear.

Are there limitations on how many fix attempts I can make for a Linear issue?

Yes, this debugging workflow enforces a strict maximum of two fix attempts per session to ensure focused issue resolution and prevent endless debugging cycles.