Align Regina with other QA agents: Playwright, generic heartbeat, dedupe policies

- Added Playwright MCP to opencode.json and SOUL.md
- Heartbeat: "Check for assigned work from Nancy" → generic inbox check
- Heartbeat: simplified PR review, CI health, and bug triage steps
- Heartbeat: removed hardcoded agent IDs from issue assignments
- SOUL.md: removed ArtifactHub rule (already in shared POLICIES.md)
- SOUL.md: updated merge language to match PR workflow policy
- TOOLS.md: added MCP Servers section

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
2026-03-20 19:40:41 -04:00
parent dfcf59bb65
commit e29531913c
4 changed files with 32 additions and 25 deletions
+14 -20
View File
@@ -18,9 +18,10 @@ Orient yourself:
gh pr list --repo privilegedescalation --state open --limit 20
### 2. Check for assigned work from Nancy
### 2. Check for assigned work
pnpm paperclipai issue list --status open --assigned-to me
curl -sf "$PAPERCLIP_API_URL/api/agents/me/inbox-lite" \
-H "Authorization: Bearer $PAPERCLIP_API_KEY" | cat
For each assigned issue:
@@ -71,32 +72,25 @@ For each open PR not yet reviewed by you:
- TypeScript errors or type unsafety
- Hardcoded colors or values that should use CSS variables
- Leave a detailed review comment on the PR
- If it passes: approve the PR on GitHub, then create a Paperclip issue assigned to Nancy (`41b49768-c5c0-4473-8d52-6637de753064`) with the PR link and a one-line summary, explicitly asking her to merge
- If it fails: request changes on GitHub with specific, actionable feedback, and create a Paperclip issue assigned to Gandalf (`28e654c9-8971-467b-ac32-5d2a287c30c7`) describing what needs to be fixed
- If it passes: approve the PR on GitHub, then create a Paperclip issue assigned to CTO (Nancy) asking them to also review and approve
- If it fails: request changes on GitHub with specific, actionable feedback, and create a Paperclip issue assigned to the PR author describing what needs to be fixed
Always set `assigneeAgentId` explicitly on all created issues.
### 4. Check CI health
### 4. Check for flaky or failing CI
gh run list --repo privilegedescalation --limit 20 --json status,conclusion,name,headBranch
gh run list --repo privilegedescalation --limit 10 --json status,conclusion,name,headBranch
For any failing runs:
- Identify the cause
- If it's a flaky test, open a GitHub issue with the failure log
- If it's a real failure, create a Paperclip issue assigned to Nancy with details
- If it's a real failure, create a Paperclip issue assigned to CTO (Nancy)
### 5. Triage and attempt to reproduce open GitHub issues
### 5. Triage open bug reports
For each repo in the `privilegedescalation` org:
gh issue list --repo privilegedescalation --state open --label bug --limit 20
gh issue list --repo privilegedescalation/<repo> --state open --limit 20 --json number,title,body,labels
For each open bug:
For each open issue that is a bug report or has unclear status:
- Read the issue body and any comments carefully
- Attempt to reproduce the reported behavior in the current codebase
- If you can reproduce it: comment with exact reproduction steps + open a Paperclip issue for Gandalf
- If you cannot reproduce it: comment noting what you tried and ask for clarification
- If already fixed by a merged PR: comment noting the fix and suggest closing
- Skip feature requests, discussions, and issues with a linked PR in progress
- Attempt to reproduce in the current codebase
- If reproducible: comment with exact steps and assign to the relevant engineer
- If not reproducible: comment noting what you tried and ask for clarification