git-rules

Files (7)

• SKILL.md
• openai.yaml · agents/
• branches-and-worktrees.md · references/
• commits.md · references/
• pull-requests.md · references/
• releases.md · references/
• resolving-merge-conflicts.md · references/

SKILL.md (first lines)

# Git Workflow

Own the repository lifecycle through one interface. Follow repository-local rules first; use these defaults when local guidance is absent.

## Select the workflow

- Branch or worktree work: read [references/branches-and-worktrees.md](references/branches-and-worktrees.md).
- Commit preparation or message generation: read [references/commits.md](references/commits.md).
- Pull request preparation or review handoff: read [references/pull-requests.md](references/pull-requests.md).
- In-progress merge or rebase conflict: read [references/resolving-merge-conflicts.md](references/resolving-merge-conflicts.md).
- Changelog, version, tag, or release: read [references/releases.md](references/releases.md).

Read only the references required by the requested operation.

## Core workflow

1. Inspect `git status -sb`, current branch, remotes, and relevant diff.
2. Separate requested changes from unrelated user changes.
3. Discover repository rules, default branch, test commands, and release conventions.
4. State the intended mutation and its exact scope before destructive, remote, or history-changing actions.
5. Execute the smallest reversible workflow.
6. Run checks proportional to risk.
7. Report branch, commit, remote target, checks, and remaining risk.

## Artifact language

- Write branch names, commit messages, issues, pull requests, review comments, changelogs, tags, release notes, and repository documentation in English.
- Keep user conversation language separate from persisted Git and GitHub artifacts.
- Use another artifact language only when the user explicitly requests it.

## GitHub authentication

Before every GitHub operation:

1. Run `gh auth status` in the execution context.
2. Confirm host, active account, token scopes, and sandbox/keyring visibility.
3. Stop when authentication is invalid or the account is wrong.
4. Recheck after authentication changes; never rely on an earlier session.

Use `gh` for GitHub operations unless a connected GitHub tool provides a safer structured operation.

## Safety invariants

- Never overwrite unrelated work or stage it silently.
- Never use destructive history or cleanup commands without explicit authority and exact targets.
- Never force-push unless the user explicitly approves the branch and reason.
- Never commit secrets, tokens, credentials, or environment-specific values.
- Prefer recoverable branches and worktrees for parallel or conflict-heavy changes.
- Treat tags and published releases as immutable; verify the target commit first.

## Completion evidence

Include only relevant evidence:

- Changed-file count and grouped summary
- Branch and commit SHA
- Checks and their outcomes
- PR or release URL
- Merge/release type and reason
- Known compatibility or rollback risk

From deepaktiwari09/team-agent-skills, MIT.

More from deepaktiwari09/team-agent-skills