hax-yax

Produces a complete health report on a skill library: per-skill structural validation followed by cross-skill analysis covering trigger conflicts, redundancy, workflow coverage gaps, and composition chains. Auto-fixes unambiguous minor structural issues (whitespace, missing optional metadata) and formats all other findings with format-review-comments. TRIGGER when: user asks to audit skills, check skill coverage, validate all skills, find gaps in skills, check for trigger conflicts, or health-check the skill library. DO NOT TRIGGER when: user asks to create, update, rename, or delete a skill (use upsert-skill instead); or to evaluate a single skill for quality (use review-skill instead).

Stages changes safely, generates a conventional-commit message from the diff, and blocks secrets or debug artifacts from being committed. TRIGGER when: user asks to commit, save changes, stage files, write a commit message, run git commit, check in my changes, or commit my work. DO NOT TRIGGER when: user asks to push, open a PR, or create a branch.

Formats code review and PR feedback using the Conventional Comments standard (label [decorations]: subject). Apply proactively whenever posting review comments or any critique of code or pull requests. Invoke directly when the user asks to format feedback, use conventional comments style, or label a review comment as blocking, suggestion, or nitpick.

Reads a structured plan from a GitHub issue and orchestrates the full delivery workflow: parses unchecked tasks in dependency order, steps through them one at a time, commits via create-commit, reviews via review-pr, and opens a PR linked back to the plan issue. Use when the user says "implement #N", "implement this plan", "execute plan #N", "work through issue #N", "implement the plan in #N", or "carry out the tasks in #N". TRIGGER when: user wants to execute or implement a plan stored as a GitHub issue. DO NOT TRIGGER when: user wants to create or update a plan (use upsert-plan instead).

Polishes drafted prose for clarity, conciseness, and consistent voice before it is posted or presented. Apply after drafting any plan, review summary, or written output to catch filler phrases, passive constructions, and inconsistent terminology. Use when the user asks to polish, clean up, improve, edit, or tighten writing — also triggered by "refine this draft", "make this clearer", or "improve my writing". Also composable: other skills invoke it as a late-stage refinement step. TRIGGER when: user asks to polish, edit, or improve prose. DO NOT TRIGGER when: user asks to format or lint code (use language-specific tools instead), or when this skill is already running as a composable step within another skill.