jackin-release-check
Use only when the user explicitly requests this skill. Runs the jackin❯ release-readiness gates.
How do I install this agent skill?
npx skills add https://github.com/jackin-project/jackin-dev --skill jackin-release-checkIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill automates release readiness checks by executing repository-specific commands and auditing project files. It uses standard development tools like Git, GitHub CLI, and Cargo to verify CI status, code formatting, and test results.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
jackin-release-check
Run the release-readiness gates. Each gate is binary — green passes, red blocks — and the release is ready only when every gate is green (warnings surface but do not block). The commands are the repo's own (from CONTRIBUTING.md merge-readiness + .github/workflows/ci.yml), never stripped-down substitutes.
When to use
- Before cutting a release, or when the operator asks whether the project is release-ready.
When NOT to use
- Cutting the release itself →
jackin-release(it runs this skill as its first gate).
Process
Run each gate in order; collect a green / red / skip verdict into a one-line-per-gate report.
-
CI gate.
gh run list --workflow=ci.yml --branch=main --limit=1 --json conclusion --jq '.[0].conclusion'— green only onsuccess. Ifdocker/construct/**ordocs/**changed since the last tag (git diff --name-only <last-tag>..HEAD -- <path>), also requireconstruct.yml/docs.ymlgreen on main.Done when every CI workflow that owns a changed path is green.
-
Static gates.
cargo fmt --check;cargo clippy --all-targets --all-features -- -D warnings. Red on any violation.Done when both exit 0.
-
Test gate.
cargo nextest run --all-features;cargo nextest run -p jackin --features e2e --profile docker-e2e. Red on any failure.Done when both suites pass.
-
Doc-link gate. Walk internal links under
docs/content/docs/(relative paths +hrefs); verify each target file exists. Red only on a broken link to a shipped page; warn on external URLs you cannot reach.Done when every internal link resolves.
-
TODO freshness. Read
TODO.mdandtodo/; flag items referencing completed work or showing no recent activity. Warn — does not block.Done when every TODO item is either live or flagged stale.
-
Security exceptions. Read
SECURITY_EXCEPTIONS.md; ask the operator whether each entry is still current. Review (blocks) until confirmed or the file is updated and re-read.Done when the operator confirms the catalog.
-
Direct-commit audit.
git log <last-tag>..HEAD --oneline --no-merges; for each commit,gh pr list --state merged --search "<sha>". Warn on commits with no PR — does not block.Done when every non-merge commit since the last tag is matched to a PR or listed as ungrouped.
Report
One line per gate: ✓ green, ✗ red (block), ⚠ warn, - skip. A red gate stops the release; a warn surfaces for the operator to accept or fix.
Common mistakes
- Running
cargo test --lockedorcargo clippy -- -D warnings(stripped flags) — those are not the repo's gates; the real commands carry--all-targets --all-featuresand usenextest. - Treating a warn as a block, or a red gate as a warn.
- Skipping the path-specific CI workflows when
docker/ordocs/changed since the last tag. - Inventing a doc-link check instead of walking the real
docs/content/docs/tree.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/jackin-project/jackin-dev/jackin-release-check">View jackin-release-check on skillZs</a>