一键导入
release
Pre-release validation for MirrorBuddy via app-release-manager subagent
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Pre-release validation for MirrorBuddy via app-release-manager subagent
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release |
| description | Pre-release validation for MirrorBuddy via app-release-manager subagent |
| allowed-tools | ["Read","Glob","Grep","Bash","Task"] |
| context | fork |
| user-invocable | true |
Pre-release validation for MirrorBuddy via app-release-manager subagent.
Project: MirrorBuddy
Branch: `git branch --show-current 2>/dev/null || echo "not a git repo"`
Uncommitted: `git status --short 2>/dev/null | wc -l | tr -d ' '` files
Version: `node -p "require('./package.json').version" 2>/dev/null || echo "unknown"`
When message contains /release or /release {version}.
Launches app-release-manager subagent with MirrorBuddy-specific validations:
await Task({
subagent_type: 'app-release-manager',
description: 'MirrorBuddy release validation',
prompt: `
RELEASE VALIDATION FOR MIRRORBUDDY
Project: MirrorBuddy
Target Version: ${version || 'auto-detect from package.json'}
Branch: ${branch}
Execute full release gate:
1. Pre-flight checks (git clean, correct branch)
2. Build validation (lint, typecheck, build)
3. Test execution (unit, E2E)
4. Security audit (secrets, dependencies)
5. Accessibility audit (WCAG 2.1 AA)
6. Compliance check (GDPR, EU AI Act)
7. Sentry + deployment configuration verification (CI + Vercel env)
8. AI tutor verification (all 26 maestri)
9. Documentation review (CHANGELOG, ADRs)
Sentry + deployment checks MUST include:
- Running \`npm run sentry:verify\` locally
- Ensuring \`.github/workflows/ci.yml\` \`sentry-config\` job installs dependencies and has \`VERCEL_TOKEN\` wired
- Verifying GitHub Actions secrets and Vercel production env contain all required Sentry and core app variables
Zero tolerance policy:
- ANY test failure = BLOCK
- ANY security issue = BLOCK
- ANY a11y violation = BLOCK
- ANY compliance gap = BLOCK
- ANY Sentry misconfiguration or missing env var = BLOCK
Output: Release report with APPROVE or BLOCK decision.
`,
});
Before running the full release gate you MAY want to sync your local .env into GitHub Actions secrets (for example after adding VERCEL_TOKEN, SENTRY_DSN, or other critical config). This is a manual, explicit step and should only be used when you are sure your local .env reflects the intended production values.
# Sync all KEY=VALUE pairs from .env to GitHub Actions secrets
# Requires GitHub CLI (gh auth login)
npm run secrets:sync
Notes:
Agent returns comprehensive report with MirrorBuddy-specific checks.
If APPROVED → version bump, git tag, CHANGELOG, GitHub release
If BLOCKED → fix issues, re-run /release
| Check | Validation |
|---|---|
| Maestri | All 26 load correctly, knowledge embedded |
| Coaches | 6 coaches with valid prompts |
| Buddies | 6 buddies with age-adaptive prompts |
| Tools | All 16 learning tools functional |
| Tiers | Trial/Base/Pro limits enforced |
| Safety | Bias detector, content filter active |
| A11y | 7 DSA profiles, instant access button |
# Fast local gate (PR-like)
npm run release:fast
# Full release validation (pre-production)
npm run release:gate
# Sentry + deployment configuration verification (must be clean)
npm run sentry:verify
# Agent-driven full release validation
/release # Auto-detect version
/release 1.5.0 # Validate specific version
app-release-managermirrorbuddy-hardening-checksthor-quality-assurance-guardiannpm run release:fast, npm run release:gateOpen a PR with MirrorBuddy checklist — ci:summary green, conventional commit, issue link, wait CI, require explicit user approval before merge.
Gate before claiming any task complete. Runs health-check.sh + ci:summary, pastes output, only then allows "done" claim.
Bootstrap isolated git worktree under ./worktrees/<task-id>. Verifies non-empty path, branch created, deps linked. Prevents working directly on main.
Comprehensive localization verification for MirrorBuddy features via npm run i18n:check
CI verification and build validation for MirrorBuddy. Use when running checks, validating builds, or verifying code quality before commits.
Release readiness verification for MirrorBuddy. Use when preparing releases, checking deployment readiness, or running pre-release validation.