release-guard

Featured

Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.

Web & Frontend 989 stars 233 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Release Guard Skill ## Workflow - Check command consistency across docs and `package.json`. - Verify architecture docs align with current code paths. - Validate that safety controls are still documented and enforced. - Report pass/fail with concrete file references. ## Focus areas - Hook flow and failure behavior. - Session/agent lifecycle semantics. - MCP safety gates and host setup instructions. - Troubleshooting accuracy. ## References - `references/release-checklist.md`

Details

Author: hoangsonww
Repository: hoangsonww/Claude-Code-Agent-Monitor
Created: 6 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Integrates with

SQLite · Database Tailwind CSS · Frontend Express.js · Backend WebSocket · API

Bundled in these plugins

Claude-Code-Agent-Monitor

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

release-ci-guardrails

XUUnity Light Unity MCP release, tag, and CI-failure guardrails; use for version bumps, release tags, GitHub Actions failures, and follow-up fixes after CI catches platform-only regressions.

3 Updated yesterday

FoxsterDev

Code & Development Listed

release-prep

Checks that the current branch is ready for a release-please release PR — conventional commit types, version manifest sync, findings-store state, and CI status. Use when preparing or verifying a release, cutting a release PR, or confirming a branch is safe to merge for release.

3 Updated today

ivuorinen

AI & Automation Listed

release-readiness

Go/no-go gate run before cutting a release, tag, or deploy. Inspects the repository and everything changed since the last release, rates each release gate against four checklists, and produces an evidence-backed GO / CONDITIONAL / NO-GO verdict. Use when you are about to ship a version and need a final readiness check, or before tagging/deploying a release.

0 Updated yesterday

jedarden