GitHub Repository
Purpose
Handle GitHub-side repository operations safely: creation, visibility, remotes, topics, PRs, and protections — always under explicit approval for outward-facing actions. Complements local git-workflow.
When to Use
- When a repo must be created, configured, or connected to a remote — with approval.
- When managing PRs/issues/protections on an existing repo.
- Not proactively; and never create a repo without explicit approval.
Inputs
- The action requested and the target owner/repo.
- Desired visibility (public/private) and settings.
- Tool/permission scope (
../../mcp/).
Discovery Questions
- Has the user explicitly approved repository creation / this remote action?
- Public or private?
- Owner/organization and naming?
- What settings (topics, default branch, protections)?
Responsibilities
- Create repos only with explicit approval, at the requested visibility.
- Configure remote, default branch, topics, description.
- Manage PRs/issues for approved work.
- Apply branch protections when requested.
- Use least-privilege tool access (
../../mcp/PERMISSION_RULES.md).
Required Workflow
- Confirm explicit approval for any outward-facing action.
- Confirm visibility, owner, and naming.
- Perform the action at minimal scope.
- Set default branch, description, topics as requested.
- Verify the result (visibility, branch, remote) and report.
Decision Rules
- Repository creation is outward-facing → requires explicit, task-specific approval.
- Default to the visibility the user specifies; if unspecified for creation, ask.
- No pushing secrets; respect secret-scanning/push-protection (fix, don't bypass).
- Prefer read-only GitHub access unless a write action is approved.
Rules
- Never create a remote repo without explicit approval (
../../system/OPERATING_RULES.md).
- Least-privilege, task-scoped tool access; disable after.
- Verify and report the actual resulting state.
Anti-Patterns
- Creating a repo speculatively or without approval.
- Bypassing push protection to force a secret through.
- Leaving broad GitHub write scope enabled across tasks.
- Assuming visibility instead of confirming.
Validation Checklist
Definition of Done
The approved GitHub operation is complete and verified (correct visibility, branch, remote, settings), performed at least privilege, with no secrets pushed and the result reported.
Related Skills
git-workflow, release-planning, security-review, project-orchestrator.
Related Knowledge
../../memory/ (owner/org conventions), ../../mcp/ (GitHub tool rules).
Related References
../../mcp/RECOMMENDED_SERVERS.md (GitHub entry).
Context Loading Guidance
- Requires: the approved action, target/visibility, tool scope.
- Does not require: application source, references, planning skills.
- May load:
../../mcp/ permission rules; git-workflow for local side.
- Stop when: the action is done and verified, or approval is pending.
Token Efficiency Guidance
Operate on the specific action and its parameters. Keep verification to the few fields that matter (visibility, branch, remote, topics).
1---2name: github-repository3description: Use to plan and (only with explicit approval) perform GitHub repository operations — creation, visibility, remotes, topics, PRs, protections. Repository creation and any outward-facing action require explicit user approval and least-privilege tool access.4---56# GitHub Repository78## Purpose910Handle GitHub-side repository operations safely: creation, visibility, remotes, topics, PRs, and protections — always under explicit approval for outward-facing actions. Complements local `git-workflow`.1112## When to Use1314- When a repo must be created, configured, or connected to a remote — **with approval**.15- When managing PRs/issues/protections on an existing repo.16- **Not** proactively; and **never** create a repo without explicit approval.1718## Inputs1920- The action requested and the target owner/repo.21- Desired visibility (public/private) and settings.22- Tool/permission scope (`../../mcp/`).2324## Discovery Questions2526- Has the user explicitly approved repository creation / this remote action?27- Public or private?28- Owner/organization and naming?29- What settings (topics, default branch, protections)?3031## Responsibilities3233- **Create repos only with explicit approval**, at the requested visibility.34- Configure **remote, default branch, topics, description**.35- Manage **PRs/issues** for approved work.36- Apply **branch protections** when requested.37- Use **least-privilege** tool access (`../../mcp/PERMISSION_RULES.md`).3839## Required Workflow40411. Confirm explicit approval for any outward-facing action.422. Confirm visibility, owner, and naming.433. Perform the action at minimal scope.444. Set default branch, description, topics as requested.455. Verify the result (visibility, branch, remote) and report.4647## Decision Rules4849- Repository creation is outward-facing → requires explicit, task-specific approval.50- Default to the visibility the user specifies; if unspecified for creation, ask.51- No pushing secrets; respect secret-scanning/push-protection (fix, don't bypass).52- Prefer read-only GitHub access unless a write action is approved.5354## Rules5556- Never create a remote repo without explicit approval (`../../system/OPERATING_RULES.md`).57- Least-privilege, task-scoped tool access; disable after.58- Verify and report the actual resulting state.5960## Anti-Patterns6162- Creating a repo speculatively or without approval.63- Bypassing push protection to force a secret through.64- Leaving broad GitHub write scope enabled across tasks.65- Assuming visibility instead of confirming.6667## Validation Checklist6869- [ ] Explicit approval obtained for outward-facing actions.70- [ ] Visibility/owner/naming confirmed.71- [ ] Least-privilege scope used.72- [ ] Default branch/topics/description set as requested.73- [ ] No secrets pushed; protections respected.74- [ ] Resulting state verified and reported.7576## Definition of Done7778The approved GitHub operation is complete and verified (correct visibility, branch, remote, settings), performed at least privilege, with no secrets pushed and the result reported.7980## Related Skills8182`git-workflow`, `release-planning`, `security-review`, `project-orchestrator`.8384## Related Knowledge8586`../../memory/` (owner/org conventions), `../../mcp/` (GitHub tool rules).8788## Related References8990`../../mcp/RECOMMENDED_SERVERS.md` (GitHub entry).9192## Context Loading Guidance9394- **Requires:** the approved action, target/visibility, tool scope.95- **Does not require:** application source, references, planning skills.96- **May load:** `../../mcp/` permission rules; `git-workflow` for local side.97- **Stop when:** the action is done and verified, or approval is pending.9899## Token Efficiency Guidance100101Operate on the specific action and its parameters. Keep verification to the few fields that matter (visibility, branch, remote, topics).
ahtishamshahzad