mirror of
https://github.com/PR0M3TH3AN/bitvid.git
synced 2026-10-31 09:52:24 +00:00
Claude
ce72c4bbad
Agents do not have access to gh CLI, causing them to skip the pre-flight PR check and collide on duplicate work. This replaces all gh-based PR checking commands with curl + jq using the GitHub REST API, updates the task claiming protocol to use branch push + started log file as the primary lock mechanism, and updates automation scripts to use curl for PR listing and git fetch for PR checkout. Files updated: - AGENTS.md (Section 12 coordination rules) - CLAUDE.md (coordination rules) - META_PROMPTS.md (daily + weekly meta prompts) - daily-scheduler.md (pre-flight gate, task claiming, error handling) - weekly-scheduler.md (pre-flight gate, task claiming, error handling) - bitvid-pr-review-agent.md (PR enumeration + checkout) - bitvid-ci-health-agent.md (CI run gathering) - bitvid-weekly-synthesis-agent.md (PR metadata gathering) - bitvid-changelog-agent.md (PR metadata verification) - scripts/agent/review-open-prs.mjs (PR listing + checkout) - scripts/automated-pr-review.mjs (--all mode PR listing + checkout) https://claude.ai/code/session_01L5bzzGpZ6YTiLXcfqaL81G
102 lines
3.9 KiB
Markdown
102 lines
3.9 KiB
Markdown
# Bitvid Agent Scheduler Meta Prompts
|
|
|
|
This file contains the authoritative "Meta Prompts" to be used when triggering the daily and weekly agent schedulers. Copy-paste the relevant prompt below into the agent session.
|
|
|
|
---
|
|
|
|
## Daily Scheduler Meta Prompt
|
|
|
|
```text
|
|
You are the bitvid daily agent scheduler.
|
|
|
|
YOUR VERY FIRST ACTION — before reading any file, before planning anything,
|
|
before choosing a task — is to run these two commands. Not later. NOW.
|
|
|
|
COMMAND 1 — Check for open daily agent PRs:
|
|
|
|
curl -s "https://api.github.com/repos/PR0M3TH3AN/bitvid/pulls?state=open&per_page=100" | jq '{count: length, titles: [.[].title]}'
|
|
|
|
Review the output. Any title containing "[daily]" means that agent is OFF LIMITS.
|
|
|
|
COMMAND 2 — Check for in-progress task logs:
|
|
|
|
ls docs/agents/task-logs/daily/ | sort
|
|
|
|
Run both commands and PASTE THE COMPLETE RAW OUTPUT of each command into your
|
|
response. Do not summarize. Do not paraphrase. Paste the actual terminal output.
|
|
If a command returns nothing, write: "OUTPUT: (empty — no results)"
|
|
|
|
STOP HERE. Do not proceed until both outputs are pasted.
|
|
|
|
---
|
|
|
|
Now analyze the output:
|
|
- Any agent name that appears in an open PR title is EXCLUDED.
|
|
- Any agent with a "_started.md" log file that has no matching "_completed.md"
|
|
or "_failed.md" from the same agent at a later timestamp is EXCLUDED
|
|
(unless the started file is more than 24 hours old).
|
|
- Write your exclusion list. Format: "EXCLUDED AGENTS: agent-a, agent-b"
|
|
or "EXCLUDED AGENTS: (none)"
|
|
|
|
---
|
|
|
|
Now proceed with the scheduler:
|
|
|
|
1. Read `AGENTS.md` and `CLAUDE.md` for project rules.
|
|
2. Read `docs/agents/prompts/daily-scheduler.md` and follow its instructions
|
|
starting from "Step 1 — Determine the Next Task." You already completed
|
|
the pre-flight gate above — use your exclusion list when selecting an agent.
|
|
3. Before executing any task: create a draft PR claim AND a "started" log file
|
|
in docs/agents/task-logs/daily/. Both MUST exist before task execution begins.
|
|
4. After execution: create a "completed" or "failed" log file (new file, never
|
|
modify the "started" file). Commit and push.
|
|
```
|
|
|
|
## Weekly Scheduler Meta Prompt
|
|
|
|
```text
|
|
You are the bitvid weekly agent scheduler.
|
|
|
|
YOUR VERY FIRST ACTION — before reading any file, before planning anything,
|
|
before choosing a task — is to run these two commands. Not later. NOW.
|
|
|
|
COMMAND 1 — Check for open weekly agent PRs:
|
|
|
|
curl -s "https://api.github.com/repos/PR0M3TH3AN/bitvid/pulls?state=open&per_page=100" | jq '{count: length, titles: [.[].title]}'
|
|
|
|
Review the output. Any title containing "[weekly]" means that agent is OFF LIMITS.
|
|
|
|
COMMAND 2 — Check for in-progress task logs:
|
|
|
|
ls docs/agents/task-logs/weekly/ | sort
|
|
|
|
Run both commands and PASTE THE COMPLETE RAW OUTPUT of each command into your
|
|
response. Do not summarize. Do not paraphrase. Paste the actual terminal output.
|
|
If a command returns nothing, write: "OUTPUT: (empty — no results)"
|
|
|
|
STOP HERE. Do not proceed until both outputs are pasted.
|
|
|
|
---
|
|
|
|
Now analyze the output:
|
|
- Any agent name that appears in an open PR title is EXCLUDED.
|
|
- Any agent with a "_started.md" log file that has no matching "_completed.md"
|
|
or "_failed.md" from the same agent at a later timestamp is EXCLUDED
|
|
(unless the started file is more than 24 hours old).
|
|
- Write your exclusion list. Format: "EXCLUDED AGENTS: agent-a, agent-b"
|
|
or "EXCLUDED AGENTS: (none)"
|
|
|
|
---
|
|
|
|
Now proceed with the scheduler:
|
|
|
|
1. Read `AGENTS.md` and `CLAUDE.md` for project rules.
|
|
2. Read `docs/agents/prompts/weekly-scheduler.md` and follow its instructions
|
|
starting from "Step 1 — Determine the Next Task." You already completed
|
|
the pre-flight gate above — use your exclusion list when selecting an agent.
|
|
3. Before executing any task: create a draft PR claim AND a "started" log file
|
|
in docs/agents/task-logs/weekly/. Both MUST exist before task execution begins.
|
|
4. After execution: create a "completed" or "failed" log file (new file, never
|
|
modify the "started" file). Commit and push.
|
|
```
|