fix

Analyze Linear issues against the Blockchain codebase and create draft pull requests for confirmed fixes.

Updated May 14, 2026

Search Tags:#debugging #pull requests #linear #issue triage #git branching #codebase validation #yarn build

Ready to run

npx skills add https://github.com/HabibTorjmen/Blockchain --skill fix-habibtorjmen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/fix
Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill fix-habibtorjmen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the back-and-forth of implementing bugfixes by validating Linear issues against the actual codebase and then producing draft pull requests with the proposed fixes.

Core Features & Use Cases

Issue triage with verdicts: Pulls full Linear issue details, locates referenced code areas, and determines whether each issue is Valid, Invalid, or Unclear.
Code-backed implementation: For confirmed issues, creates issue-based branches, applies fixes, and verifies them via the project build.
Draft PR generation: Pushes changes and opens draft PRs that reference the originating Linear issue for traceability.

Quick Start

Ask the skill to fix Linear issues A-690, A-691, and A-692 by analyzing each one against the repository and creating draft PRs for the issues you confirm as valid.

Frequently Asked Questions about fix

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

FAQPage Schema

How do I automate Linear issue triage and generate draft pull requests for confirmed bugs?▼

Automating Linear issue triage involves analyzing reported defects against your codebase to determine validity, implementing fixes on separate branches, running yarn build for validation, and opening GitHub draft PRs that reference the originating Linear tickets.

What is the workflow for fixing multiple Linear issues sequentially in a repository?▼

Fixing multiple Linear issues sequentially requires triaging each ticket against the codebase, branching deterministically from merge-train/spartan, applying code changes, executing yarn build for validation, and generating a draft PR for each confirmed issue.

Can I validate Linear bug fixes against my codebase before opening a pull request?▼

Yes, validating Linear bug fixes before opening a pull request is possible by applying code changes to an issue-based branch and executing yarn build to verify the project build succeeds before pushing changes and creating a draft PR.

Does automated issue triage classify Linear tickets as valid or invalid?▼

Automated issue triage classifies Linear tickets by pulling full issue details, locating referenced code areas, and determining whether each reported defect is Valid, Invalid, or Unclear before proceeding with code-backed implementation.

When should I not use automated draft PR generation for issue tracking?▼

You should not use automated draft PR generation when Linear issues lack sufficient context for codebase analysis, resulting in an Unclear verdict, or when manual architectural decisions are required before implementing code changes.