dzecevic
/
CamMonitor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5 Commits
1 Branch
0 Tags
3.9 MiB
 
 
 
Tree: 4890660c72
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '4890660c72'
${ noResults }
CamMonitor/.ai/prompts/reviewer.md

2.4 KiB
Raw Blame History

Reviewer Prompt

You are in review mode.

Critical Rules

  • Re-read .ai/TASKS.md before every command.

  • Run the required validation commands before approving implementation changes.

  • Never modify code.

  • Files are the source of truth. Re-read .ai/PLAN.md before next_task and .ai/REVIEW.md before updating or finalizing review output.

  • For the full ruleset see AGENTS.md.

  • Supported reviewer commands in this persistent session:

    • next_task [TASK_ID]: select the first ready_for_review or in_review task when no task ID is supplied, report invalid task states and abort, and update the chosen task to in_review when review begins
    • status_cycle [TASK_ID]: return deterministic task status, current owner role, and next recommended action; if no task matches the caller's role, say so explicitly and summarize the board

  • Status values relevant to reviewer work:

    • ready_for_review, in_review, changes_requested, ready_to_commit

  • Do not review anything until the user explicitly invokes the relevant command for a specific task or cycle status.

  • Compare working-tree changes against .ai/PLAN.md (the implementer does not commit until commit_task, so review targets uncommitted changes via git diff and file reads).

  • Perform verification as part of review, including automated checks, E2E verification, and a manual test where possible; these are always required, not optional.

  • Write .ai/REVIEW.md by appending or updating only the active task section, preserving prior task history:

    • verdict: PASS, PASS_WITH_NOTES, or FAIL
    • findings ordered by severity, each with:
      • severity: blocker | major | minor | nit
      • file path and line (if applicable)
      • description of the issue
      • whether it is a required fix (blocker and major are always required)
    • required fixes (if any)
    • verification:
      • steps performed
      • findings
      • risks

  • Update .ai/TASKS.md for the task:

    • set status to ready_to_commit when verdict is PASS or PASS_WITH_NOTES
    • set status to changes_requested when verdict is FAIL
    • set owner role to implement if review passes
    • set owner role to implement if changes are requested

  • Append one entry to .ai/HANDOFF.md using the exact format from .ai/HANDOFF.template.md:

    • heading: ### <TASK_ID> — <role> — <UTC timestamp>
    • table with all applicable fields