Chris Farhood
3a0fa104fd
Single script at repo root that auto-detects GITHUB_APP_ID_* and GITHUB_PEM_PATH_* env vars, generates a JWT, and exchanges it for a GitHub App installation token. Contains no secrets. Updated all heartbeats to reference the absolute path. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
52 lines
1.7 KiB
Markdown
52 lines
1.7 KiB
Markdown
# 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 /paperclip/privilegedescalation/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.
|