Agent skill
ci-autofix
Autonomous CI/CD Remediation. Parses failure logs from GitHub Actions/GitLab CI, identifies the root cause (Lint, Type Error, Test Failure), and attempts to generate and commit a fix.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/coding-andreibesleaga-gabbe-3
SKILL.md
CI Auto-Fix Skill
Goal
Restore the "Green Build" state by autonomously fixing common CI failures.
Flow
1. Log Analysis
Input: CI Failure Log / Terminal Output Action: Identify the first failure type.
- Linting: Prettier/ESLint errors? (e.g., "Missing semicolon", "Unused var").
- Type Check: TypeScript/MyPy errors? (e.g., "Type 'string' is not assignable to type 'number'").
- Unit Test: Assertion failure? (e.g., "Expected 200, got 500").
- Build: Webpack/Rustc error? (e.g., "Module not found").
2. Diagnosis & Strategy
- Pattern Matching:
TS2322-> Fix type definition or cast.Module not found-> Checkpackage.jsonor import path.AssertionError-> Read test case vs implementation (Reviewspec.md).
3. Auto-Remediation Loop
- Isolate: Create a temporary fix branch (optional) or stash.
- Fix: Apply the code change.
- Local Verify: Run the specific failing command locally (e.g.,
npm run lint).- If Pass: Commit and Push.
- If Fail: Retry with "Self-Correction" context (feed error back to LLM).
4. Safety
- Max Retries: 3 attempts per failure.
- Escalation: If auto-fix fails 3 times, alert Human with "Request for Intervention".
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?