fix-error
Skill4 starsChanged 6 months agoMITView on GitHub
Use when a build fails or there are unresolved errors. Reads .agents/errors/errors.md, investigates root cause, applies fix, verifies build, and logs the resolution.
In this repository76 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/components.mdcCursor rule
- .cursor/rules/currency.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/file-structure.mdcCursor rule
- .cursor/rules/forbidden-patterns.mdcCursor rule
- .cursor/rules/mvvm-architecture.mdcCursor rule
- .cursor/rules/pricing-display.mdcCursor rule
- .cursor/rules/scope.mdcCursor rule
- .cursor/rules/swift-conventions.mdcCursor rule
- accessibilitySkill
- animationsSkill
- apple-developer-authSkill
- apple-signinSkill
- app-store-preflightSkill
- asc-app-create-uiSkill
- asc-aso-auditSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-metadata-yamlSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-screenshot-resizeSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- ascSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-whats-new-writerSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- billing-finance-calculatorSkill
- buildSkill
- business-modelSkill
- chartsSkill
- consolidate-errorsSkill
- content-composerSkill
- crashSkill
- debuggingSkill
- feature-directory-structureSkill
- feedback-statesSkill
- formsSkill
- foundation-modelsSkill
- hapticsSkill
- healthkitSkill
- layoutSkill
- listsSkill
- navigationSkill
- notificationsSkill
- onboarding-questionnaireSkill
- onboardingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read .agents/errors/errors.md — find [UNRESOLVED] entries
- Distinctive: line 13
If no unresolved entries, check the latest build output for errors
- Very specific: line 20
Read the error ledger for past [RESOLVED] and [CONSOLIDATED] entries with similar patterns:
- Distinctive: line 25
If a match exists, apply the known fix pattern — don't reinvestigate.
- Distinctive: line 29
If no prior match:
- Distinctive: line 30
Read the failing file at the reported line
- Distinctive: line 31
Read imports, type definitions, related files
- Distinctive: line 39
If multiple files need changes, make all changes before rebuilding
- Distinctive: line 43
Run the build. If it fails again:
- Very specific: line 69
After resolving, mention: "Run /consolidate-errors to feed this fix back into rules/skills."
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix Error
Investigate and resolve unresolved build errors from the error ledger.
Quick Start
- Read
.agents/errors/errors.md— find[UNRESOLVED]entries - If no unresolved entries, check the latest build output for errors
- For each error, follow the resolution workflow below
Resolution Workflow
1. Check History First
Read the error ledger for past [RESOLVED] and [CONSOLIDATED] entries with similar patterns:
- Same file or module?
- Same error type (type mismatch, concurrency, missing reference)?
- Same crash signature?
If a match exists, apply the known fix pattern — don't reinvestigate.
2. Investigate
If no prior match:
- Read the failing file at the reported line
- Read imports, type definitions, related files
- Classify the error by category
- Identify root cause (not just the error message — the actual WHY)
3. Fix
- Edit the failing file(s)
- Fix the root cause, not the symptom
- If multiple files need changes, make all changes before rebuilding
4. Verify
Run the build. If it fails again:
- Is it the same error? (fix didn't work — try another approach)
- Is it a new error? (fix introduced a regression — fix that too)
- Max 3 attempts. If still failing, report findings and stop.
5. Update the Ledger
In .agents/errors/errors.md, change the entry from [UNRESOLVED] to [RESOLVED] and fill in:
## [RESOLVED] <timestamp> — <brief description>
- **Error:** `<error message>`
- **File:** `<file:line>`
- **Category:** `<category from classification>`
- **Symptom:** <what it looked like>
- **Root Cause:** <what actually caused it>
- **Misleading Signal:** <what made this confusing, if applicable>
- **Fix:** <what was changed and why>
- **Files Changed:** <list of modified files>
- **Key Diagnostic:** <the single most important clue>
- **Prevention Rule:** <one-sentence rule that would prevent this>6. Suggest Consolidation
After resolving, mention: "Run /consolidate-errors to feed this fix back into rules/skills."
Error Categories
| Category | Pattern | Common Root Cause |
concurrency/async-render | EXC_BREAKPOINT + AsyncRenderer | UIKit code on wrong thread |
concurrency/isolation | Actor-isolated property error | Swift 6 Sendable violation |
type-mismatch | Cannot convert value of type | Wrong type, missing conformance |
missing-reference | Use of unresolved identifier | Missing import, typo, deleted symbol |
missing-type | Cannot find type in scope | Missing import or undeclared type |
ambiguous-type | Ambiguous use of | Duplicate type declarations |
api-mismatch | Has no member | Deprecated or wrong API |
file-structure | File > 200 lines | Needs splitting |
swiftdata | ModelContext thread crash | Wrong actor for context |
theme | Hardcoded color/font/spacing | AppTheme token not used |
If You Can't Fix It
Report what you found:
## Error Investigation (Unresolved)
- **Error:** [description]
- **Investigated:** [what you checked]
- **Hypotheses:** [possible causes ranked by likelihood]
- **Blocked By:** [what prevented the fix]
- **Suggested Next Step:** [what a human should try]Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

