fw-review
Installation
SKILL.md
Entry contract
- Invoked by: controller after build/validate milestones or explicit review request
- Preconditions: App directory with
manifest.json;fdkavailable or user consented to fw-setup install - Returns:
done(review report emitted) |blocked(missing fdk / app dir) |escalate(unrecoverable manifest issues) - On complete: hand control back to the controller — controller offers publish; do not invoke fw-publish from this skill
- Session:
session-read.shat start; on pass —session-write.sh <app-dir> --merge-json '{"progress":{"milestones":["review_passed"],"phase":"review"}}' step=reviewed
fw-review
This is an automated pipeline. After the app directory is determined (Q1 pre-flight below), do not ask further questions or interact with the user for disambiguation — execute the remaining phases silently and produce only the formatted App Review Result block in rules/report.md. Do not prefix or suffix that block with commentary (no Pass/N/A rationales, script notes, or pipeline status).
Exception: If fdk is missing, follow FDK CLI availability below (STOP → offer /fw-setup-install → optional y/n) — that interaction overrides “silent only” until the CLI exists or the user declines install.
Pre-flight: determine app directory (Q1)
Before the workflow, follow the same steps as fw-app-dev /fdk-fix Step 1: Determine app directory: