affiliatemcp: Skill for Claude Code

Prepare a pull request for review

Follow the delivery and review protocol in AGENTS.md. This skill prepares a reviewable handoff; it never merges a PR.

1. Inspect before changing PR state

Gather evidence, do not rely on the existing PR description:

git status --short --branch
git fetch origin
git diff --stat origin/main...HEAD
git diff origin/main...HEAD
git log --oneline origin/main..HEAD
gh pr view --json number,title,url,isDraft,baseRefName,headRefName,mergeable,mergeStateStatus,reviewDecision,reviewRequests,statusCheckRollup,body
gh pr list --state open --json number,title,url,isDraft,reviewDecision,reviewRequests
gh pr checks

If the PR targets a base other than main, compare against that base instead. Inspect the complete diff, including generated files and lockfiles. If the branch has no PR, complete the initial classification and verification, then create a draft PR using the applicable template. Never open a new PR as ready for review.

Classify and record:

• one user outcome;
• intended customer journey and affected cohort;
• the owning architectural layer;
• dependencies and whether they are merged;
• workstream, dependency graph, lane, and semantic conflict domains;
• public contracts changed;
• risk domains and failure modes;
• deliberately excluded scope;
• changed-file count and additions.

2. Apply the readiness gates

Keep the PR draft and explain the next action when any gate fails:

• The branch has conflicts, failed or pending required CI, or an unmerged dependency.
• A product or architecture decision required by this PR remains unresolved. Propose a small decision PR using the decision template. Keep this PR to discovery or an explicitly disposable prototype; do not prepare production foundations or implementation for review.
• The diff combines independent outcomes or separable high-risk domains. Propose concrete PR slices.
• The review brief is incomplete or does not match the diff.
• The agent has not inspected the complete diff.
• The PR exceeds 1,000 additions or 20 files without a credible split rationale.