agentleFS
mustafahasanainmustafahasanain/frappe-workflow/skills/codex-review/SKILL.md

codex-review

Skill0 starsChanged 3 months agoMITView on GitHub

Codex review lifecycle - build the review bundle, generate the prompt, parse APPROVED/CHANGES_REQUIRED results, run the review-fix loop, and invalidate approval via the implementation fingerprint.

91 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

Files
SKILL.md

Codex Review Skill

Manages the external Codex review of a completed implementation. Codex reviews only — it never modifies files; the bundle says so explicitly.

When to Use

  • review action (stage implementation/review_fixes, completion gate passed) → bundle + prompt (references/review-prompt-generation.md).
  • apply-review action (stage codex_review) → parse result (references/review-result-parsing.md).
  • Stage review_fixes → fix loop (references/review-fix-loop.md).
  • Any post-approval change → (references/approval-invalidation.md).

Inputs

  • Passing completion gate; docs/ai-context/TASK_PLAN.md; the implementation summary at docs/ai-context/implementation-summary.md; Git state; for apply-review, the raw Codex result text or file.

Outputs

  • docs/ai-context/reviews/round-NNN-prompt.md (via bin/frappe-workflow review bundle, which secret-scans and embeds the fingerprint).
  • docs/ai-context/reviews/round-NNN-result.md — the original result, preserved verbatim.
  • State updates: round, prompt/result paths, fingerprint, status (pending → changes_required → … → approved), approved_at.

Preconditions

  • Bundle: validate completion-gate passes.
  • Result parsing: a prompt for the current round exists and state is codex_review.
  • Approval acceptance: current fingerprint == recorded fingerprint.

Stopping Conditions

  • APPROVED accepted → finalization (feature-changelog + project-context updates, review record) → validate finalization-gate → ready_for_commit. Done.
  • CHANGES_REQUIRED → review_fixes; loop continues until approved.
  • Malformed result → reject with the format requirements; stay in codex_review; never guess a status.

Prohibited

  • Generating a prompt without a passing completion gate.
  • Accepting any status other than exactly APPROVED / CHANGES_REQUIRED.
  • Inventing, dropping, or "interpreting away" findings; the original result file is never edited.
  • Accepting approval whose fingerprint mismatches the working tree.
  • Applying a finding without validating it against the repository first.

Shared Rules

shared-workflow-rules.md, security-rules.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.