GitHub Fix CI: purpose and common use cases
GitHub Fix CI comes from the community repository composio-community/awesome-codex-skills, with its canonical skill file recorded at gh-fix-ci. For GitHub Fix CI, that repository is authoritative; Artifiner uses the verified Code Review, DevOps, Development metadata from this record for discovery and does not infer ratings or unsupported behavior.
Where GitHub Fix CI fits in an agent workflow
GitHub Fix CI is a Codex skill for code review. GitHub Fix CI's role is practical rather than generic: it gives an agent task-specific instructions for examining changes before they are merged or shipped. In the catalog it is discoverable around github actions, ci, and debugging, which are useful starting points when the user knows the outcome they need but not the exact capability name. GitHub Fix CI is represented as a standalone source-backed capability in the Artifiner catalog.
What to check before using GitHub Fix CI
Use GitHub Fix CI when the job maps to pull-request review, CI feedback and code-quality checks. For GitHub Fix CI, a sensible workflow is to start with the task, check that the skill matches the project and tools involved, and then follow the upstream instructions rather than treating the directory description as executable documentation. Artifiner keeps the GitHub Fix CI source link visible so you can inspect its current SKILL.md before relying on behavior that may change as the repository evolves.
Inspect failing GitHub Actions, summarize failures, and propose targeted fixes.