architecture-principle…
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Called by review-pr after its reviewer fleet and judgment pass return: consolidates their findings against the PR''s history into the set of comments worth posting — pruning what the PR already covers, merging duplicates, subordinating defects under premise questions, bounding
Claude Code
$ npx -y skills add doodledood/manifest-dev --skill review-pr-holistic --agent claude-code
Codex
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a codex -y
Cursor
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a cursor -y
Gemini CLI
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a gemini-cli -y
GitHub Copilot
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a github-copilot -y
OpenCode
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a opencode -y
Windsurf
$ npx skills add doodledood/manifest-dev --skill review-pr-holistic -a windsurf -y
name: review-pr-holistic description: 'Called by review-pr after its reviewer fleet and judgment pass return: consolidates their findings against the PR''s history into the set of comments worth posting — pruning what the PR already covers, merging duplicates, subordinating defects under premise questions, bounding to the reviewed range, and rewriting every body in the caller''s voice. Not for direct use.' user-invocable: false
Turn a pile of findings into the comments a careful reviewer would actually post. This skill edits and consolidates; it generates nothing new and posts nothing itself.
**Receives.** Fleet findings — severity-graded defect findings from the reviewer dimensions, with dimension and severity retained, the caller's chosen acceptance and publication policies, with findings filtered only by that policy after checking consequence; correctness or safety failures and broken binding promises received as Low regraded from evidence before that filtering — and the judgment assessment with its findings — a distinct non-severity class defined by `../review-pr-judgment/SKILL.md`, already synthesized to one question per root; the PR history (all comments and threads on the PR, including ours from any prior pass, the author's recent commit messages on the branch, the PR description); bundle context for each linked PR (diff, description, top-level conversation — no inline review comments from linked PRs); the manifest if present; the reviewed range for this invocation — the code the fleet's defect findings are bounded to; the caller's voice profile — its rules for how a posted comment reads; and any truncation the caller did, to carry forward.
Preserve Low findings retained by the caller's chosen policy; consolidation does not impose its own severity cutoff.
**Does, in this order:**
**Returns.** The comments to post (anchor plus voice-compliant body), the summary header text if any, truncation notes, a brief dropped-findings tally with the dominant reasons, and the retained judgment assessment for the operator. Rewriting preserves its recommendation, evidence and uncertainty; a firm recommendation can be phrased directly without the voice's banned softeners.
Hand your agent a task. Get back work you can trust. manifest-dev is a set of free, open-source skills for coding agents.
Architecture principles for manifest-dev: how its maintainer wants skills, wrappers, references, state and the workflow…
Ship a change to a file setup-project copies or emits into projects (ADR_FORMAT.md, NORTH_STAR_FORMAT.md, the verification…
Design principles for manifest-dev: how its maintainer wants the visual and interaction design guidance the plugin ships, and the…
Harden a manifest-dev task guidance file for one-shot quality — either /define''s quality-gate/Default set or figure-out''s probe…
Analyze Claude Code sessions to learn what went right/wrong and suggest high-confidence improvements to skills. Use when asked to…
The red-flag lists mirrored between figure-out''s and define''s task files, so a change to one side lands on the other. Use when…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.