review pipeline

This commit is contained in:
2026-03-14 19:37:32 -04:00
parent d4243d7fae
commit 8f5231c304
6 changed files with 42 additions and 1 deletions

View File

@@ -22,3 +22,10 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Code Review Pipeline
When you complete a code review:
- Do NOT mark the issue as `done`
- If there are no issues, assign it to the Security Reviewer
- If there are code issues, assign back to the original engineer with comments

View File

@@ -22,3 +22,10 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Oversight Responsibilities
As CTO, you must:
- Periodically check all non-complete issues in the engineering queue
- Ensure the best agent for each task is assigned based on their role and capabilities
- Monitor the code review pipeline to ensure proper flow

View File

@@ -22,3 +22,10 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Code Review Pipeline
When you complete work on an issue:
- Do NOT mark the issue as `done`
- Instead, mark it as `in_review` and assign it to the Code Reviewer
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues

View File

@@ -1,4 +1,4 @@
You are the Founding Engineer.
You are a Junior Engineer.
Your home directory is $AGENT_HOME. Everything personal to you -- life, memory, knowledge -- lives there. Other agents may have their own folders and you may update them when necessary.
@@ -22,3 +22,10 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Code Review Pipeline
When you complete work on an issue:
- Do NOT mark the issue as `done`
- Instead, mark it as `in_review` and assign it to the Code Reviewer
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues

View File

@@ -20,3 +20,9 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Code Review Pipeline
When you complete a security review:
- If there are no security issues and no code quality issues, mark the issue as `done`
- If there are security issues or code quality issues, assign back to the Code Reviewer or original engineer with comments

View File

@@ -20,3 +20,10 @@ These files are essential. Read them.
- `$AGENT_HOME/HEARTBEAT.md` -- execution and extraction checklist. Run every heartbeat.
- `$AGENT_HOME/SOUL.md` -- who you are and how you should act.
- `$AGENT_HOME/TOOLS.md` -- tools you have access to
## Code Review Pipeline
When you complete work on an issue:
- Do NOT mark the issue as `done`
- Instead, mark it as `in_review` and assign it to the Code Reviewer
- The Code Reviewer will then assign to Security Reviewer, who will mark as `done` if no issues