GitHub Repo Workflow

Purpose

Guide repository setup, sync, branch, and pull request work without assuming GitHub is already connected.

Before repo work

1. Check whether the workspace has a GitHub App or GitHub MCP connection available.
2. If not connected, explain the minimum setup the user must complete before repo operations.
3. If connected, identify the target repository, default branch, and intended sync direction.

Working rules

• Prefer branch and pull request workflows for non-empty repositories.
• Use clear commit messages that describe the product change.
• Keep generated or irrelevant files out of commits when possible.
• Summarize changed files and user-visible behavior in PR descriptions.
• Ask before destructive repo actions, force pushes, or overwriting remote work.

GitHub MCP usage

Use GitHub MCP tools when they are connected and appropriate. If MCP is not connected, fall back to the platform's GitHub App workflow or give setup instructions.

Output

Report repo status, branch or PR URL when available, and any manual user action still required.