Scrubs McBarkley
6bfd1b6c30
Export full company configuration including agents, skills, and memory files as of 2026-04-13. Adds missing agents (barkley-trimsworth, daisy-clippington, shedward-scissorhands) and updates existing agent instructions and skill definitions. Co-Authored-By: Paperclip <noreply@paperclip.ing>
47 lines
2.4 KiB
Markdown
47 lines
2.4 KiB
Markdown
# GitHub
|
|
|
|
#### GitHub is the primary source of truth. Paperclip issues must have a corresponding GitHub issue, if one does not exist it should be created. Both GitHub and Paperclip issues should remain open until the work is completed, reviewed, approved, merged, and quality assurance has been performed.
|
|
|
|
### You have GitHub access via a GitHub App with credentials stored in a file and environment variables. A GitHub MCP server and the gh cli are available.
|
|
All changes must happen via pull request.
|
|
Tag @cpfarhood in all pull requests for **visibility only** (cc, not review request).
|
|
|
|
### GitHub Authentication
|
|
|
|
**Invoke the `github-app-token` skill** before any GitHub operation. The skill provides step-by-step instructions for generating a short-lived installation token and setting `GH_TOKEN`. Follow whatever the skill says.
|
|
|
|
**NEVER run `gh auth login`.** It triggers an interactive device-auth flow that hangs headless agents for minutes.
|
|
|
|
> **Token expiry:** The generated token expires after ~1 hour. Re-invoke the skill to regenerate if your session runs long enough that it may have expired.
|
|
|
|
### Creating Pull Requests
|
|
|
|
Use the `gh` CLI or the GitHub MCP server to create pull requests. Always cc @cpfarhood for visibility — do **not** request review from @cpfarhood.
|
|
|
|
```bash
|
|
gh pr create --title "..." --body "... cc @cpfarhood"
|
|
```
|
|
|
|
### PR Review & Merge Policy
|
|
|
|
Branch protection requires **2 approving GitHub reviews** before merge. The required reviewers are:
|
|
|
|
1. **CTO** (The Dogfather) — technical review and approval
|
|
2. **QA** (Lint Roller) — quality review and approval
|
|
|
|
**@cpfarhood is not a reviewer.** Do not request review from or tag @cpfarhood as a required approver. The board is cc'd for visibility only.
|
|
|
|
When a PR is ready for review:
|
|
- Request review from the CTO and QA agents on GitHub
|
|
- If reviews are dismissed (e.g., after a force-push or rebase), request fresh reviews from CTO and QA — not from the board
|
|
- Once both approvals are in place, the CTO or CEO may merge
|
|
|
|
### CTO Review Gate
|
|
|
|
CTO review requires QA approval as a precondition. Before reviewing any PR, confirm that:
|
|
|
|
1. **Lint Roller** (Senior QA Engineer) has an active GitHub approval on the PR.
|
|
|
|
If this gate is missing, skip the PR and move on.
|
|
|
|
> **Note:** CEO UAT runs **after** CEO merges and deploys to dev — not before CTO review. Requiring CEO UAT sign-off before CTO review creates a deadlock. CEO validates the live deployed app on dev, not the PR itself. |