Assess Expo release readiness with evidence-based priorities.
Verify a versioned software release is genuinely complete — tickets actually implemented (not just closed), docs discoverable (not just present), CI green on all matrix platforms, coverage gated, security scan clean, rollback path tested, and version metadata consistent. Produces a structured READY / NOT READY / BLOCKED report with evidence-backed findings and action items.
Read-only preflight for Google Play, Amazon, Microsoft Store, itch.io or Apple: assets, signing, permissions, versions and blockers.
需求写了一半、规则没补齐、验收条件不清楚，就准备交给开发？ Requirement Ready AI 会从业务目标、功能范围、业务规则、验证、权限、UI、API、异常与边界条件等角度检查需求完整度，并补齐 User Story、Acceptance Criteria、QA Test Cases 与风险。 帮助你在进入开发前，先确认需求是否真的 Ready。
Paste a diff and get a risk-ranked checklist of what it'll actually break — hidden dependencies, config drift, and blast radius that static analysis can't see, checked before you ship.
Before you install a third-party skill, scan it. Skill Security Audit audits a skill package — code and SKILL.md prose alike — across 10 risk classes: plain-text instruction poisoning, hard-coded secrets, prompt injection including delegated sub-agent calls, destructive commands, data exfiltration, download-and-execute chains, over-broad permissions, and disclosure gaps. Judged under your agent's permissions. Reports findings with file and line evidence. Never runs the code it audits.
Audits your test suite's output for silently vanished tests, unexplained skips, and suspiciously fast runs — turns green CI into a real signal.
Defensive application-security auditing: turns a repo, manifest, or code snippet into an actionable report—dependency vulnerabilities, leaked secrets, insecure code patterns, and config hardening—mapped to OWASP Top 10 and ranked by severity. Finds risk and the fix only, never attack content.
A scan tells you what is wrong. This tells you what to do. Same engine as the ADA Website Risk Scanner — 14 WCAG 2.2 AA check families. But instead of a defect list, you get a work plan: findings grouped into batches, ordered by exposure reduced per hour of developer time, each with before/after code, effort estimate, required skill, and a verification step. Three phases. Quick wins first. A project manager can assign it as-is.