| name | forge-release-check |
| description | Pre-release checklist - changelog, version, CI/CD, breaking changes. Trigger when user types /forge-release-check or requests a pre-release check.
|
/forge-release-check
Pre-release checklist using AI reasoning.
Command
/forge-release-check [path] [--quick|--deep] [--markdown|--json] [--verbose]
Options
[path] — Target directory (default: current directory)--quick — Fast scan, focus on critical issues only--deep — Thorough scan, check all patterns--markdown — Output as markdown (default)--json — Output as JSON--verbose — Include detailed evidence
Purpose
Pre-release verification:
- Changelog verification
- Version validation
- CI/CD pipeline check
- Deployment configuration
- Breaking change detection
Workflow
Step 1: Understand Project
Use shared/analyzer/ to detect:
- Project type
- Version management
- CI/CD configuration
Step 2: Run Release Checks
Execute analysis prompts:
- Changelog Verification (
prompts/changelog-verification.md)
- Version Validation (
prompts/version-validation.md)
- CI/CD Check (
prompts/ci-cd-check.md)
- Deployment Config (
prompts/deployment-config.md)
- Breaking Change Detection (
prompts/breaking-change-detection.md)
Step 3: Generate Report
Use shared/report/ to generate:
- Release Readiness Score (0-100)
- Checklist status
- Blocking issues
Output Format
Follow the markdown report format generated by shared/report/markdown.ts. It MUST use the following layout:
Release Check Report
Project: [Project Name]
Path: [Project Path]
Language: [Primary Language]
Framework: [Detected Framework (optional)]
Date: [Timestamp]
Score
[Score]/100 (Grade: [Grade])
| Severity | Count |
|---|
| 🔴 Critical | [count] |
| 🟠 High | [count] |
| 🟡 Medium | [count] |
| 🔵 Low | [count] |
| ⚪ Info | [count] |
Executive Summary
Found [total] issues: [count] critical, [count] high, [count] medium, [count] low, [count] info.
🔍 Detailed Findings
[Severity Group (e.g. 🔴 Critical)]
| Title | Location | Description | Impact |
|---|
| [Finding Title] | [file-name]:[line] | [Description] | [Impact] |
📂 Code Evidence
Finding #[number]: [Finding Title]
[code snippet]
