JStepUX

Lists the agent bash utility scripts in scripts/agent/ with their headers and usage lines. Use this at the start of a session, when decomposing a new task, or whenever you catch yourself about to reach for raw tool calls that one of these scripts already composes. Refreshes your working memory of the bash layer so you don't reinvent what's already there.

A mandatory quality gate that enforces test coverage, localization, documentation, spec archival, and commit hygiene after any implementation work. Use this skill whenever code changes are complete and about to be committed — trigger on phrases like "I'm done", "ready to commit", "finished implementing", "task complete", "wrap up", "ship it", "PR ready", or any signal that implementation is finished and the work is moving toward version control. Also trigger when reviewing someone else's completed work before merge. This skill should fire even if the user doesn't explicitly ask for a quality check — if implementation just finished, this gate applies. Do NOT skip steps. Do NOT self-certify. Every item requires evidence.

Discovery-phase skill for symptom-shaped tasks. Use when the user hands you a vague problem, a bug report, a console error, or a "this is broken" style request rather than a well-specified feature. Produces a grounded problem brief you can either act on directly or hand to the project-coordinator agent as a sharp, pre-diagnosed task spec. Closes the gap between "here's a symptom" and "here's a decomposable plan".

Prepares a release. Reads the changelog entries that pre-commit-qa has accumulated since the last release marker, cross-checks against git for any bypassed commits, proposes a semver bump, and — on explicit user approval — inserts a release marker, bumps the version, commits, and tags. Does not push and does not deploy. Use before running the project's deploy command, or when the user signals release intent ("ready to deploy", "time to ship", "cut a release", "write the changelog", "release prep"). The authoring side of the release pipeline — complements `pre-commit-qa` (which gates individual commits) by gating the batch that becomes a release.

A mandatory quality gate that enforces verification, documentation, spec archival, and commit hygiene before work lands in version control. This skill is invoked by the DEVELOPER only — NEVER proactively by the agent, no matter how finished the implementation looks. The developer routinely interposes a cross-model peer review (Codex) between "implementation finished" and "ready to land"; an agent-initiated gate commits unreviewed work and forces a second landing pass. When implementation finishes: verify (tests/typecheck/lint), present the work, and WAIT. The developer running /pre-commit-qa IS the commit order — once invoked, walk every gate with evidence and, if all pass, proceed to commit without further approval pauses. Do NOT skip steps. Do NOT self-certify. Every item requires evidence.

Lists the agent bash utility scripts in scripts/agent/ with their headers and usage lines. Use this at the start of a session, when decomposing a new task, or whenever you catch yourself about to reach for raw tool calls that one of these scripts already composes. Refreshes your working memory of the bash layer so you don't reinvent what's already there.

A mandatory quality gate that enforces test coverage, localization, documentation, spec archival, and commit hygiene after any implementation work. Use this skill whenever code changes are complete and about to be committed — trigger on phrases like "I'm done", "ready to commit", "finished implementing", "task complete", "wrap up", "ship it", "PR ready", or any signal that implementation is finished and the work is moving toward version control. Also trigger when reviewing someone else's completed work before merge. This skill should fire even if the user doesn't explicitly ask for a quality check — if implementation just finished, this gate applies. Do NOT skip steps. Do NOT self-certify. Every item requires evidence.

Prepares a release. Reads the changelog entries that pre-commit-qa has accumulated since the last release marker, cross-checks against git for any bypassed commits, proposes a semver bump, and — on explicit user approval — inserts a release marker, bumps the version, commits, and tags. Does not push and does not deploy. Use before running the project's deploy command, or when the user signals release intent ("ready to deploy", "time to ship", "cut a release", "write the changelog", "release prep"). The authoring side of the release pipeline — complements `pre-commit-qa` (which gates individual commits) by gating the batch that becomes a release.

A mandatory quality gate that enforces test coverage, documentation, spec archival, and commit hygiene after any implementation work. Use this skill whenever code changes are complete and about to be committed — trigger on phrases like "I'm done", "ready to commit", "finished implementing", "task complete", "wrap up", "ship it", "PR ready", or any signal that implementation is finished and the work is moving toward version control. Also trigger when reviewing someone else's completed work before merge. This skill should fire even if the user doesn't explicitly ask for a quality check — if implementation just finished, this gate applies. Do NOT skip steps. Do NOT self-certify. Every item requires evidence.

A mandatory quality gate that enforces test coverage, documentation, spec archival, and commit hygiene after any implementation work. Use this skill whenever code changes are complete and about to be committed — trigger on phrases like "I'm done", "ready to commit", "finished implementing", "task complete", "wrap up", "ship it", "PR ready", or any signal that implementation is finished and the work is moving toward version control. Also trigger when reviewing someone else's completed work before merge. This skill should fire even if the user doesn't explicitly ask for a quality check — if implementation just finished, this gate applies. Do NOT skip steps. Do NOT self-certify. Every item requires evidence.