Run any Skill in Manus with one click

execute-review

Stars0

Forks1

UpdatedMay 21, 2026 at 01:47

Execute code review for implementation changes against TechSpecs, task files, project rules, and project skills. Use when Codex is asked to review code, analyze git diff, verify tests, check rules compliance, validate TechSpec or task adherence, identify code smells, or create codereview.md at the project root or under tasks/prd-[feature-name]/.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rodrigobranas

rodrigobranas/aidev_axon_7

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	execute-review
description	Execute code review for implementation changes against TechSpecs, task files, project rules, and project skills. Use when Codex is asked to review code, analyze git diff, verify tests, check rules compliance, validate TechSpec or task adherence, identify code smells, or create codereview.md at the project root or under tasks/prd-[feature-name]/.

Execute Review

Core Workflow

Use this skill to review implementation changes against the expected technical specification, task scope, project standards, and tests.

Read resources/execute-review.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/code-review-report-template.md only when generating the final codereview.md report. Treat that file as the required review report template standard.

Execution Rules

Read the TechSpec and Tasks for the target feature when available.
Read relevant project rules and project skills before judging compliance.
Use git diff to analyze changed code.
Read the full modified files, not only the diff.
Verify implementation adherence to the TechSpec and completed Tasks.
Run the relevant project tests and reject the review if required tests fail.
Check for rule violations, missing tests, code smells, security risks, and performance issues.
Save the final report in codereview.md at the project root, or tasks/prd-[feature-name]/codereview.md when the review is feature-specific.
Generate the final report from resources/code-review-report-template.md.

Expected Inputs

Typical input is a feature directory, branch/diff context, or request such as:

"Use $execute-review for tasks/prd-team-invitations."
"Review the current git diff against the TechSpec and tasks."
"Run a code review and create codereview.md."

If the feature context is unclear, inspect tasks/prd-* directories and the current git diff, then ask for clarification only when multiple plausible feature folders exist.

More from this repository

same repository

create-prd

rodrigobranas/aidev_axon_7

Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

2026-05-210

create-tasks

rodrigobranas/aidev_axon_7

Create implementation task lists and individual task files from an existing PRD and Tech Spec. Use when Codex is asked to write, generate, create, draft, or update feature tasks, implementation tasks, task breakdowns, delivery plans, or task files based on tasks/prd-[feature-name]/prd.md and tasks/prd-[feature-name]/techspec.md.

2026-05-210

create-techspec

rodrigobranas/aidev_axon_7

Create implementation-ready Technical Specifications from existing PRDs using a required analyze-research-clarify-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a Tech Spec, technical specification, implementation specification, architecture spec, or engineering plan based on tasks/prd-[feature-name]/prd.md and save it as tasks/prd-[feature-name]/techspec.md.

2026-05-210

execute-bugfix

rodrigobranas/aidev_axon_7

Fix documented QA bugs for a feature by reading bugs.md, qa.md, PRD, Tech Spec, and tasks; planning fixes by severity; implementing root-cause fixes; adding regression tests; validating with project tests and Playwright for UI bugs; and updating bugfix artifacts. Use when Codex is asked to fix bugs, resolve QA findings, address failed QA, or complete bugfix work in tasks/prd-[feature-name]/.

2026-05-210

execute-qa

rodrigobranas/aidev_axon_7

Execute QA validation for a completed feature against its PRD, Tech Spec, and tasks using Playwright MCP, accessibility checks, visual review, bug documentation, and a final QA report. Use when Codex is asked to test, QA, validate, approve, reject, or verify a feature implementation in tasks/prd-[feature-name]/.

2026-05-210

execute-review

rodrigobranas/aidev_axon_7

Execute a code review for implemented work by analyzing git diff, reading modified files, checking project rules and skills, verifying Tech Spec and task adherence, running tests, identifying code quality issues, and saving a code review report. Use when Codex is asked to review code, validate implementation quality, approve changes, or produce codereview.md for a feature or project change.

2026-05-210

name	execute-review
description	Execute code review for implementation changes against TechSpecs, task files, project rules, and project skills. Use when Codex is asked to review code, analyze git diff, verify tests, check rules compliance, validate TechSpec or task adherence, identify code smells, or create codereview.md at the project root or under tasks/prd-[feature-name]/.

Execute Review

Core Workflow

Use this skill to review implementation changes against the expected technical specification, task scope, project standards, and tests.

Read resources/execute-review.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/code-review-report-template.md only when generating the final codereview.md report. Treat that file as the required review report template standard.

Execution Rules

Read the TechSpec and Tasks for the target feature when available.
Read relevant project rules and project skills before judging compliance.
Use git diff to analyze changed code.
Read the full modified files, not only the diff.
Verify implementation adherence to the TechSpec and completed Tasks.
Run the relevant project tests and reject the review if required tests fail.
Check for rule violations, missing tests, code smells, security risks, and performance issues.
Save the final report in codereview.md at the project root, or tasks/prd-[feature-name]/codereview.md when the review is feature-specific.
Generate the final report from resources/code-review-report-template.md.

Expected Inputs

Typical input is a feature directory, branch/diff context, or request such as:

"Use $execute-review for tasks/prd-team-invitations."
"Review the current git diff against the TechSpec and tasks."
"Run a code review and create codereview.md."

If the feature context is unclear, inspect tasks/prd-* directories and the current git diff, then ask for clarification only when multiple plausible feature folders exist.