ci-fix

Runs a seven-gate CI quality sequence with auto-fix and blocker reporting.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/ByronWilliamsCPA/plugin --skill ci-fix-byronwilliamscpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-fix
Source: https://github.com/ByronWilliamsCPA/plugin/tree/main/plugins/wff-code/skills/ci-fix
Command: npx skills add https://github.com/ByronWilliamsCPA/plugin --skill ci-fix-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CI pipelines fail for many small reasons—formatting, lint, test failures, security findings—and fixing them one CI round-trip at a time is slow. This Skill runs the full local gate sequence in a fixed order, auto-fixes what it can, and reports a complete status picture before you commit. ## Core Features & Use Cases - Seven-Gate Sequence: Runs ruff format, ruff lint, qlty check, pre-commit, pytest, bandit, and pip-audit in a fixed order, re-running each gate after every fix attempt. - Auto-Fix with Blocker Tracking: Applies deterministic fixes (ruff format, ruff check --fix), marks gates that fail twice as BLOCKER, and always reports all seven gates in a status table. - Operational Runbooks: Includes diagnosed patterns for GitHub Actions failures such as stale-base failures, frozen merge-commit reruns, startup_failure contract mismatches, and workflow authoring anti-patterns. - Use Case: Your pre-commit hooks and tests are failing before a release. Invoke the skill to run every gate locally, auto-fix lint and format issues, identify the two failing tests as blockers, and get a commit offer only when all required gates are green. ## Quick Start Ask the AI to run ci-fix to execute all CI gates, auto-fix what it can, and report any remaining blockers.

Frequently Asked Questions about ci-fix

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

FAQPage Schema
How do I fix failing CI gates locally before pushing?▼

Run the full gate sequence locally in a fixed order: ruff format, ruff lint, qlty check, pre-commit, pytest, bandit, then pip-audit. Auto-fix formatting and lint with ruff, re-run each gate after fixing, and only commit when all required gates pass.

How to auto-fix ruff lint and format errors in Python?▼

Use `uv run ruff format .` for deterministic formatting fixes and `uv run ruff check --fix .` for auto-fixable lint rules. Remaining unfixable rules require manual edits, after which you re-run the gate to confirm it passes.

Why does pip-audit still report a CVE after upgrading a package with uv?▼

`uv lock --upgrade-package` updates the lock file but not the active virtualenv. Run `uv sync --reinstall-package <name>` afterward so pip-audit and tests see the upgraded version instead of the stale one.

Why does gh run rerun not pick up a fixed workflow file?▼

For pull requests, GitHub replays the original frozen merge commit, so rerun uses the workflow as it existed at merge time. Push a new commit to the PR branch to trigger a synchronize event that builds a fresh merge commit against the current base.

Can a CI failure be caused by the base branch instead of my PR?▼

Yes. A branch behind its base can fail gates on issues the base already fixed, and path-filtered jobs can hide regressions on main. Reproduce the failure against clean main and rebase before treating it as a defect in your changes.