adinsights-release-readiness
Synthesize ADinsights release readiness from router, scope, contract, docs, and optional validation checks. Use when deciding go/no-go readiness, release gate status, or pre-merge release risk.
Best use case
adinsights-release-readiness is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Synthesize ADinsights release readiness from router, scope, contract, docs, and optional validation checks. Use when deciding go/no-go readiness, release gate status, or pre-merge release risk.
Teams using adinsights-release-readiness should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adinsights-release-readiness/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adinsights-release-readiness Compares
| Feature / Agent | adinsights-release-readiness | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Synthesize ADinsights release readiness from router, scope, contract, docs, and optional validation checks. Use when deciding go/no-go readiness, release gate status, or pre-merge release risk.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ADinsights Release Readiness ## Overview Aggregate readiness evidence and return a gate decision packet across scope, contract integrity, tests, observability, security, and runbook/documentation readiness. This skill is advisory-first and supports optional command execution. ## Context Load Order 1. Open `AGENTS.md`. 2. Open `docs/runbooks/release-checklist.md`. 3. Open `docs/runbooks/deployment.md`. 4. Open `docs/runbooks/operations.md`. 5. Open `docs/project/api-contract-changelog.md`. 6. Open `docs/project/integration-data-contract-matrix.md`. 7. Open `references/release-gates.yaml`. ## Inputs Primary packet inputs: - Router packet (`--router-packet`) - Scope packet (`--scope-packet`) - Contract packet (`--contract-packet`) Optional execution input: - `--run-checks` to execute configured readiness commands. - `--changed-files-from-git` to include diff context in documentation/compliance reasoning. ## Gate Model Return exactly one status: - `GATE_PASS` - `GATE_WARN` - `GATE_BLOCK` Gate dimensions: - `scope_control` - `contract_integrity` - `test_coverage` - `observability` - `security_pii_secrets` - `runbook_ops_readiness` - `documentation_completeness` - `rollout_rollback_plan` Gate dimension statuses: - `PASS` - `INFO` (pending evidence/action; does not escalate release status) - `WARN` - `BLOCK` ## Output Contract Return a release decision packet with: - `schema_version` (`1.1.0`) - `release_status` - `gate_results` - `blocking_issues` - `warnings` - `pending_items` - `required_approvers` - `required_artifacts` - `recommended_next_action` - `evidence` entries (`type`, `value`, `strength`, `source`) - `executive_summary` ## CLI Interface Use `scripts/evaluate_release_readiness.py`: - `--prompt "<text>" --format json|markdown` - `--router-packet "<path>"` - `--scope-packet "<path>"` - `--contract-packet "<path>"` - `--run-checks` - `--changed-files-from-git` One-command full-chain preflight (router -> scope -> contract -> release): - `scripts/run_preflight_skillchain.py --prompt "<text>" --format json|markdown` - Optional: `--path <path>` (repeatable), `--changed-file <path>` (repeatable), `--changed-files-from-git` - Optional: `--run-checks` to execute release optional checks - Optional: `--output-dir <dir>` to persist packet JSON files ## Default Behavior - Synthesis-first packet evaluation. - Optional checks only when `--run-checks` is set. - Advisory wording only; no hard-block language. ## Maintenance - Keep `references/release-gates.yaml` aligned with release checklist/runbooks. - Run `scripts/validate_release_gates.py` after rules edits. - Run `scripts/run_release_golden_tests.py` before syncing. - Sync with `scripts/sync_to_codex_home.sh`.
Related Skills
release-manager
Assists with Morphir release management, including pre-release verification, changelog generation, and release coordination. Use when preparing releases, checking release readiness, or managing version bumps.
ash-library-release
Manages version releases for ash_cookie_consent Elixir library including CHANGELOG updates, version bumping, quality checks, Hex.pm publishing, and git tagging. Use when user asks to "release", "publish to hex", "bump version", "create release", or "prepare for publishing".
android-release-notes-structure
Create Play Store release notes directory structure with locale templates (Fastlane metadata)
chronos-release
Release a new version of the AllSource Chronos monorepo. Bumps versions across all services (Rust, Go, Elixir), runs full CI to green, creates a single squashed commit with an annotated immutable tag. Use when the user says "release", "new version", "bump version", "tag a release", "cut a release", or "make a release". Argument is the version number (e.g., "0.10.4") or "patch"/"minor"/"major" for auto-increment.
readiness-report
Evaluate how well a codebase supports autonomous AI development. Analyzes repositories across nine technical pillars (Style & Validation, Build System, Testing, Documentation, Dev Environment, Debugging & Observability, Security, Task Discovery, Product & Analytics) and five maturity levels. Use when users request `/readiness-report` or want to assess agent readiness, codebase maturity, or identify gaps preventing effective AI-assisted development.
appstore-readiness
Expert iOS App Store submission and approval system. 9 specialized agents providing senior App Review Team-level expertise across compliance, design, privacy, monetization, metadata, technical requirements, timing, rejection recovery, and learning. Triggers on keywords like app store, iOS submission, apple review, app rejection, aso, privacy manifest, privacy labels, ATT, iap, in-app purchase, subscription, storekit, review guidelines, HIG, testflight, app store connect.
autonomous-agent-readiness
Assess a codebase's readiness for autonomous agent development and provide tailored recommendations. Use when asked to evaluate how well a project supports unattended agent execution, assess development practices for agent autonomy, audit infrastructure for agent reliability, or improve a codebase for autonomous agent workflows. Triggers on requests like "assess this project for agent readiness", "how autonomous-ready is this codebase", "evaluate agent infrastructure", or "improve development practices for agents".
release-automation
Automate complete release process with versioning and publishing
homebrew-release
Create a new version release for a Homebrew formula in the homebrew-tools tap. Handles git tagging, GitHub releases, SHA256 computation, and formula updates. Use when the user wants to publish a new version of a tool in their Homebrew tap.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
claw-release
Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.
ARW Release Manager
Build and release manager for ARW CLI package. Handles local development, testing, building, documentation, version tagging, and publishing to npm and crates.io. Use when developing locally, running tests, building packages, releasing new versions, or publishing packages.