unac-fix-blockers

Orchestrate fixes for blocking issues from code review reports.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/uesleinasch/unac-agents --skill unac-fix-blockers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unac-fix-blockers
Source: https://github.com/uesleinasch/unac-agents/tree/main/skills-claude/unac-fix-blockers
Command: npx skills add https://github.com/uesleinasch/unac-agents --skill unac-fix-blockers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates fixes for blocking issues identified in a code review report, coordinating per-issue fixes and build validation.

Core Features & Use Cases

  • Enumerate all blocking issues from the code review report and compile a fix plan.
  • Create per-issue fix reports and dispatch unac-code-fix for each issue, then run a global build to validate changes.
  • Enforce a hard two-iteration limit and hand off progress updates back to the reviewer workflow.

Quick Start

Provide the item-id and ensure the code review report is available at .unac/{item-id}/{item-id}_code_review_report.md, then run this skill to start fixes.

Frequently Asked Questions about unac-fix-blockers

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

FAQPage Schema
How do I automate fixes for blocking issues found in a code review report?

Automating fixes for blocking code review issues involves reading the review report, creating per-issue fix plans, dispatching fix tasks, and running a global build to validate all changes.

What is the best way to coordinate code fixes and build validation for blocking review items?

Coordinating code fixes and build validation requires orchestrating per-issue fixes from the review report and executing a global build after all dispatches complete to ensure stability.

How many fix iterations are allowed when resolving blocking code review issues?

Resolving blocking code review issues enforces a hard two-iteration limit, allowing a maximum of two fix dispatch attempts per issue before handing off progress updates.

Do I need a specific file format to start automating blocking issue resolution?

Automating blocking issue resolution requires the code review report to be available as a markdown file at the .unac/{item-id}/{item-id}_code_review_report.md path.

Why does my automated build fail after dispatching fixes for blocking code review issues?

Automated build validation runs globally after all per-issue fixes are dispatched, so build failures indicate that the applied code fixes did not resolve the blocking issues within the iteration limit.

Can I dispatch multiple fixes for a single blocking issue during code review automation?

Code review automation enforces a single fix dispatch per blocking issue, strictly limiting each identified problem to one fix attempt per iteration to ensure controlled progress updates.