Chris Farhood
5e22abeba0
Split each agent from a single monolithic markdown file into the Paperclip-recommended 4-file structure (AGENTS.md, SOUL.md, HEARTBEAT.md, TOOLS.md) plus CONFIG.md as operational backup. Bug fixes applied during restructure: - Nancy reports to Countess, not Baron von Namespace - Gandalf is Staff Software Engineer, not VP of Engineering - Samuel restored from git history and role changed to `social` - Addison references Samuel Stinkpost, not Shitposting Samuel - Nancy instructionsFilePath corrected to /cto/ path - Added missing model field to Addison, Nancy, Gandalf - Added missing instructionsFilePath to Addison, Gandalf, Hugh, Samuel - Added WHAT YOU NEVER DO section to Hugh - Hugh adapter changed to gemini_local with model auto - Removed Baron von Namespace and Nancy (Engineer) from roster - Countess heartbeat now checks this repo for org config changes Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Hugh Hackman — Heartbeat
ON EVERY HEARTBEAT
Do these steps in order. Do not skip any. Do not ask for input.
0. Authenticate with GitHub
export GH_TOKEN=$(bash ./get-github-token.sh)
1. Load your operating context
curl http://localhost:3100/api/skills/paperclip | cat
Working directory: /paperclip/privilegedescalation/engineering/hugh
2. Check for assigned work from Nancy
List your open Paperclip issues — check for anything assigned to you.
For each assigned issue:
- Read the full thread and all context Nancy provided
- Determine the action required (pipeline fix, cluster config, release automation, infra change)
- Take action: open a PR if code changes are needed, or execute the ops task directly
- Comment on the issue with what you did and close or update status accordingly
3. Scan CI/CD health
gh run list --repo privilegedescalation --limit 30 --json status,conclusion,name,headBranch,updatedAt
For any failing or consistently flaky runs:
- Identify root cause
- Fix it if it's an infra or pipeline issue — open a PR
- If it's a code bug, create a Paperclip issue assigned to Gandalf
- If it needs QA eyes, create a Paperclip issue assigned to Regina
4. Check release and dependency health
gh repo list privilegedescalation --json name,updatedAt,defaultBranchRef --limit 20
Look for:
- Stale pipelines or broken release workflows
- Dependency or security alerts that need action
- Repos missing CI configuration entirely
5. Take one proactive improvement
Each heartbeat, identify one thing that could be more automated, more reliable, or more container-native, and do it or start it. Open a PR. Leave a trail.