Ultra-Fix Protocol
Address findings from a preceding ultrareview validation. Work through each finding systematically, implementing fixes with precision and completeness.
Scope
$ARGUMENTS
If no scope specified, address all findings from the most recent ultrareview output.
Plan Mode: Ultrareview analyzed a plan/proposal. Findings reference architecture or design decisions. The plan file exists in .claude/plans/ or similar.
Implementation Mode: Ultrareview analyzed code changes. Findings reference specific file:line locations. Code files exist and need modification.
Adapt your fix strategy accordingly.
Finding Categories
| Marker |
Category |
Priority |
| CRITICAL |
Blockers |
Fix immediately |
| ERRORS (HIGH) |
Bugs/Issues |
Fix before proceeding |
| ERRORS (MEDIUM/LOW) |
Issues |
Address systematically |
| ALIGNMENT ISSUES |
Pattern conflicts |
Align with codebase conventions |
| MISSING |
Gaps |
Fill identified gaps |
| NEEDS VALIDATION |
Uncertainties |
Investigate, then fix or dismiss |
| IMPROVEMENTS |
Enhancements |
Implement beneficial changes |
Skip VALIDATED items — these confirm correct behavior.
If ultrareview reported no actionable findings, confirm the context is ready and exit.
Fix Protocol
Phase 1: Extract and Prioritize
Parse the ultrareview output and create a task list for tracking progress. Use TaskCreate for each finding.
Phase 2: Plan-Mode Fixes
For plans/proposals:
- Locate the relevant section in the plan file
- Understand the original intent
- Craft a revision that addresses the finding while preserving intent
- After all fixes, verify the plan still flows logically
Phase 3: Implementation-Mode Fixes
For code/configuration:
- Read target files completely before editing
- Design fixes that integrate cleanly
- Implement with minimal disruption to working code
- Verify fixes don't break existing functionality
Phase 4: Verification
For Plans: Re-read the complete plan, verify internal consistency.
For Implementations: Run relevant tests, check for linting/type errors, verify integration.
Output Format
Summary Report
RESOLVED
- [List each addressed finding with brief description of fix]
DEFERRED (if any)
- [Finding]: [Reason for deferral]
INTRODUCED CHANGES
- [Any additional changes beyond the findings]
VERIFICATION STATUS
- Tests: [pass/fail/not run]
- Lint: [clean/issues]
- Integration: [verified/needs manual check]
Execution Rules
- One finding at a time: mark in_progress, fix, verify, mark completed
- Atomic changes: each fix should be independently valid
- No scope creep: only address items from ultrareview findings
- Document decisions: if you skip or defer, explain why
- Preserve intent: fixes solve problems without changing goals
- Use provided code snippets from ultrareview as starting points
- Verify file:line references before editing
- Never create unit tests, mocks, or synthetic-data test fixtures — e2e with real data only
1---2name: ultrareview-fix3description: |4 Use when working through the findings of a preceding ultrareview validation — systematically addressing the5 reported errors, alignment issues, gaps, and improvements by priority and applying each fix to the plan or the6 code. Trigger phrases include "ultrareview-fix", "fix the review findings", "address the ultrareview", and7 "apply those fixes". Expects an ultrareview summary in the conversation; the `ultrareview` skill produces it.8allowed-tools: Read, Write, Edit, Glob, Grep, Bash, TaskCreate, TaskUpdate, TaskList, TaskGet9license: MIT10metadata:11 author: AeyeOps12 version: "0.5.2"13 summary: Applies the findings of an ultrareview validation to the plan or code, in priority order.14---1516# Ultra-Fix Protocol1718Address findings from a preceding ultrareview validation. Work through each finding systematically, implementing fixes with precision and completeness.1920## Scope21$ARGUMENTS2223If no scope specified, address all findings from the most recent ultrareview output.2425<context_detection>26Determine what you're fixing:2728**Plan Mode:** Ultrareview analyzed a plan/proposal. Findings reference architecture or design decisions. The plan file exists in `.claude/plans/` or similar.2930**Implementation Mode:** Ultrareview analyzed code changes. Findings reference specific `file:line` locations. Code files exist and need modification.3132Adapt your fix strategy accordingly.33</context_detection>3435<investigate_before_fixing>36Before modifying any artifact:371. Re-read target files from disk — even if they appear in conversation context.38 Files may have changed since the ultrareview read them, and stale context39 produces incorrect fixes. Trust the current file, not the earlier Read result.402. Understand the context around each finding413. Verify the finding is still applicable given the current file contents424. Plan fixes that don't introduce new issues43</investigate_before_fixing>4445## Finding Categories4647| Marker | Category | Priority |48|--------|----------|----------|49| CRITICAL | Blockers | Fix immediately |50| ERRORS (HIGH) | Bugs/Issues | Fix before proceeding |51| ERRORS (MEDIUM/LOW) | Issues | Address systematically |52| ALIGNMENT ISSUES | Pattern conflicts | Align with codebase conventions |53| MISSING | Gaps | Fill identified gaps |54| NEEDS VALIDATION | Uncertainties | Investigate, then fix or dismiss |55| IMPROVEMENTS | Enhancements | Implement beneficial changes |5657Skip VALIDATED items — these confirm correct behavior.5859If ultrareview reported no actionable findings, confirm the context is ready and exit.6061## Fix Protocol6263### Phase 1: Extract and Prioritize64Parse the ultrareview output and create a task list for tracking progress. Use TaskCreate for each finding.6566### Phase 2: Plan-Mode Fixes6768For plans/proposals:69- Locate the relevant section in the plan file70- Understand the original intent71- Craft a revision that addresses the finding while preserving intent72- After all fixes, verify the plan still flows logically7374### Phase 3: Implementation-Mode Fixes7576For code/configuration:77- Read target files completely before editing78- Design fixes that integrate cleanly79- Implement with minimal disruption to working code80- Verify fixes don't break existing functionality8182### Phase 4: Verification8384**For Plans:** Re-read the complete plan, verify internal consistency.8586**For Implementations:** Run relevant tests, check for linting/type errors, verify integration.8788## Output Format8990### Summary Report9192**RESOLVED**93- [List each addressed finding with brief description of fix]9495**DEFERRED** (if any)96- [Finding]: [Reason for deferral]9798**INTRODUCED CHANGES**99- [Any additional changes beyond the findings]100101**VERIFICATION STATUS**102- Tests: [pass/fail/not run]103- Lint: [clean/issues]104- Integration: [verified/needs manual check]105106## Execution Rules1071081. One finding at a time: mark in_progress, fix, verify, mark completed1092. Atomic changes: each fix should be independently valid1103. No scope creep: only address items from ultrareview findings1114. Document decisions: if you skip or defer, explain why1125. Preserve intent: fixes solve problems without changing goals1136. Use provided code snippets from ultrareview as starting points1147. Verify file:line references before editing1158. Never create unit tests, mocks, or synthetic-data test fixtures — e2e with real data only116117<post_fix_workflow>118After completing all fixes, inform the user they can run ultrareview again to verify fixes and catch any issues introduced by the changes.119</post_fix_workflow>
AeyeOps