- Home
- Skills
- Agents & Orchestration
- Release Readiness Evidence Review
More screenshots
Works with the AI Agents you already use
Release Readiness Evidence Review
Diagnose and repair release readiness evidence, test results, approvals, known risks, rollback evidence, dependencies, and unresolved gates.
$1
Release Readiness Evidence Review
Example session with this skill installed
Review the release evidence in the /deploy and /logs directories for version 2.4.0. Check for test results, approval signatures in the metadata, and the rollback manifest.
- Read your context and instructions
- Compiled the release readiness evidence
I have analyzed the artifacts in /deploy and /logs for version 2.4.0. I found verified build logs and deployment manifests, but identified a discrepancy in the rollback procedures and a missing security sign-off.
Release Readiness Review: v2.4.0
Source Register
| ID | Source | Type | Timestamp |
|---|---|---|---|
| SRC-01 | /logs/build-2.4.0.log | Build Log | 2023-10-27 09:15 UTC |
| SRC-02 | /deploy/manifest.yaml | K8s Manifest | 2023-10-27 10:02 UTC |
| SRC-03 | /deploy/approvals.json | Metadata | 2023-10-27 10:45 UTC |
| SRC-04 | /deploy/rollback.sh | Shell Script | 2022-05-12 14:20 UTC |
Findings & Evidence Status
| Requirement | Status | Evidence Reference | Notes |
|---|---|---|---|
| Unit Tests | PASS | SRC-01 | 452 tests passed, 0 failures. |
| Integration Tests | PASS | SRC-01 | API suite completed in 122s. |
| Engineering Approval | VERIFIED | SRC-03 | Signed by dev-lead-01. |
| Security Review | MISSING | N/A | No signature found for sec-ops role. |
| Rollback Plan | CONFLICT | SRC-04 | Script references v2.2.0 variables; likely stale. |
Identified Gaps
Stale Rollback Evidence: rollback.sh has not been updated in 18 months and targets an incompatible environment schema.
2.
Missing Security Gate: The approvals.json file contains a null field for the security_signoff key, which is a mandatory gate.
3.
Dependency Ambiguity: manifest.yaml uses a floating tag for the auth-service sidecar rather than a pinned SHA.
Next steps
- Update
rollback.shto reflect the current schema for v2.4.0. - Obtain the
security_signoffhash from the SecOps dashboard. - Pin the
auth-serviceimage inmanifest.yamlto a specific immutable digest.
Connects securely to your tools. The creator never sees your data.
About this skill
Release Readiness Evidence Review is a bounded ToolForge Labs workflow. Diagnose and repair release readiness evidence, test results, approvals, known risks, rollback evidence, dependencies, and unresolved gates. Works from full repositories or partial context such as snippets, logs, configuration, traces, and architecture notes. Produces concrete repairs or evidence-backed review outputs while preserving existing product/security policy.
It works from a full repository or partial evidence such as snippets, logs, configuration, traces, tickets, and architecture notes. The skill preserves existing product and security policy, separates verified facts from assumptions, avoids invented execution claims, and produces concrete repair or review steps with focused deterministic validation or traceable evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Cannot verify production systems, external services, or facts that are not present in supplied evidence. With partial context it returns bounded diagnosis/review, explicit assumptions, and a deterministic validation plan rather than claiming successful execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.