Orchestrator

# Git Operations

Use this skill before running git or GitHub commands. Keep commands simple, auditable, and token-safe.

## Core Rules

- Activate this skill when the request mentions git, GitHub, clone, branch, worktree, commit, push, PR, merge, or repository auth.
- Use `cwd` or command-native flags like `git -C <dir>` instead of `cd`.
- Avoid multiline backslash command chains in the bash tool; run one clear command per tool call.
- Never put GitHub tokens in URLs, command text, logs, branch names, commit messages, or PR bodies.
- Inspect `git status --short --branch` before staging, committing, pushing, or merging.
- Keep discovery bounded: never use broad recursive dumps like `ls -R`; prefer git-aware or max-depth listings.
- Split local changes (`git add`, `git commit`) from network operations (`git push`, `gh pr create`, `gh pr merge`).
- Use dry-runs for risky push or merge operations when the operator has not explicitly requested the final action.

## Documentation Index

- `references/sandbox-command-shape.md`: bash tool command shape, `cwd`, and rejected patterns.
- `references/github-auth.md`: token-safe GitHub auth behavior and `gh` usage.
- `references/clone-fetch-pull.md`: read-only remote operations.
- `references/branch-worktree.md`: branch/worktree setup and cleanup.
- `references/commit-push.md`: status, staging, commit, push, and dry-run flow.
- `references/pr-review-merge.md`: PR creation, review, merge, and post-merge checks.
- `references/recovery.md`: handling common failures and recovery steps.
- `references/new-project.md`: creating a new local project and pushing to GitHub.

Read only the reference needed for the current operation with `read_skill_resource`.

# Vercel Operations

Use this skill before running `vercel` or `vc` commands. Requires `vercelAccess` to be set in Settings → Tool permissions.

## Core Rules

- Activate this skill when the request mentions vercel, deploy, promote, rollback, alias, Vercel logs, or Vercel env.
- NEVER echo, log, or print VERCEL_TOKEN. It is injected by the sandbox and must never appear in output or command text.
- For production deployments (`--prod`/`--production`): confirm with the operator before running. Prefer a preview deploy first.
- Use preview deploys (`vercel deploy`) for testing changes before promoting to production.
- Treat `vercel remove` / `vercel rm` as destructive — confirm before executing.
- Keep commands simple: one operation per tool call.

## Documentation Index

- `references/vercel-auth.md`: token-safe auth behavior and required permission profile.
- `references/monitoring.md`: inspect, logs, list, and status commands.
- `references/deploying.md`: deploy, promote, rollback, alias workflow.
- `references/env-management.md`: env ls, add, rm, pull.

Read only the reference needed for the current operation with `read_skill_resource`.