Files

T

Pawla Abdul 3032f2fc0e chore: sync company/ export snapshot with current configuration

- Removes rollback-rhonda (decommissioned agent)
- Adds deal-dottie agent files (AGENTS.md, mcp.json)
- Updates .paperclip.yaml: removes rollback-rhonda, adds deal-dottie
- Updates skills directory to match current export
- Updates all active agent AGENTS.md files and memory/life files

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-04-06 08:59:29 +00:00

2.2 KiB

Raw Blame History

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

Use the github-app-token skill for GitHub access. The skill is instructions only — there is no script to run. Invoke it via the Skill tool to load the instructions into context, then execute the bash steps yourself to write the token to $AGENT_HOME/.gh-token and authenticate with gh auth login --with-token. Clean up the token file after use.

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.

gh pr create --title "..." --body "... cc @cpfarhood"

PR Review & Merge Policy

Branch protection requires 2 approving GitHub reviews before merge. The required reviewers are:

CTO (Savannah Savings, you) — technical review and approval
QA (Checkout Charlie) — 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 both QA gates as a precondition. Before reviewing any PR, confirm that:

Checkout Charlie (QA Engineer) has an active GitHub approval on the PR.
Rollback Rhonda (User Acceptance Tester) has signed off — either via a Paperclip comment on the issue or a PR comment confirming UAT passed.

If either QA gate is missing, skip the PR and move on.

2.2 KiB Raw Blame History