MANDATORY: Follow the complete shared lifecycle contract in ${CLAUDE_PLUGIN_ROOT}/skills/shared/run-lifecycle.md with declared skill agnix-fix.

Agnix-Fix Skill

MANDATORY: READ ENTIRE FILE before composing user-facing prose: $PWD/skills/shared/readability-style.md.

Private convenience alias for fixing agent-sh/agnix issues from a fork clone. Goes beyond larch:alias flag-forwarding by (a) fetching the upstream issue body so /implement does not have to research it, (b) provisioning the skip-changelog label on the fork (idempotent), and (c) baking CI-monitoring guidance into the prompt so the orchestrator interprets the fork's deterministic add-to-project failure correctly.

Not shipped to other plugin consumers — placed under .claude/skills/agnix-fix/ (dev-only).

CI-monitoring contract

Forks of agent-sh/agnix cannot access org-level secrets. The add check (run by add-to-project.yml via pull_request_target) requires secrets.PROJECT_TOKEN and always fails on fork PRs in ~2s with Input required and not supplied: github-token (the action's parameter name, not the auto-provided GITHUB_TOKEN). The orchestrator MUST treat this as expected-to-fail and not loop on it.

A green run on the fork means: ci (agnix + test) green, claude-review green, Build docs site green, Verify Changelog skipped (via [skip changelog] title token or skip-changelog label). If any of those four fail, that is a real failure to fix. The add failure is ignored. The upstream PR (later opened by the operator against agent-sh/agnix) runs on agent-sh's runners with all secrets, so add-to-project succeeds there.

For issues touching only knowledge-base/, crates/agnix-rules/, or website/docs/rules/generated/ (rule-metadata or generated-docs corrections), prefix the PR title with [skip changelog]. For issues materially changing behavior or user-facing surfaces, do NOT add the prefix and author a CHANGELOG.md entry as part of the implementation.

/implement exit routing (delegated runs)