# Git Github Flow

> Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.

- **Type:** Skill
- **Install:** `agentstack add skill-dominiktobureto-awesome-grok-build-git-github-flow`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [DominikTobureto](https://agentstack.voostack.com/s/dominiktobureto)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [DominikTobureto](https://github.com/DominikTobureto)
- **Source:** https://github.com/DominikTobureto/awesome-grok-build/tree/main/.grok/skills/git-github-flow

## Install

```sh
agentstack add skill-dominiktobureto-awesome-grok-build-git-github-flow
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Git GitHub Flow

Turn local changes into a clean, reviewable contribution.

## Grok Build Mode

- Use Plan Mode before rewriting commits, rebasing, force-pushing, or touching release branches.
- Use subagents for merge readiness:
  - `diff`: changed files and intent.
  - `tests`: verification status and gaps.
  - `docs`: README/changelog/release notes.
  - `risk`: risky files, migrations, auth, config.
- Arena-style PR description: generate 2-3 PR narratives and choose the clearest.
- Human-in-the-loop: never push, force-push, publish, or merge without explicit user approval.

## Workflow

1. Inspect `git status`, branch, remotes, and recent commits.
2. Separate unrelated changes.
3. Stage intentionally.
4. Write a concise commit message:
   - imperative subject;
   - why in body when useful;
   - tests run.
5. Draft PR description with:
   - summary;
   - screenshots/demo if relevant;
   - verification;
   - risks;
   - follow-ups.
6. Push only after approval.

## GitHub Best Practices

- Link issues when known.
- Keep PRs small and coherent.
- Do not include secrets or local config.
- Do not mark generated files for review unless necessary.
- Address review comments with targeted commits.

## Example Prompts

```text
Use git-github-flow. Prepare a clean commit and PR description from my current diff. Do not push yet.
```

```text
Use git-github-flow to respond to PR review comments. Preserve unrelated user changes.
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [DominikTobureto](https://github.com/DominikTobureto)
- **Source:** [DominikTobureto/awesome-grok-build](https://github.com/DominikTobureto/awesome-grok-build)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-dominiktobureto-awesome-grok-build-git-github-flow
- Seller: https://agentstack.voostack.com/s/dominiktobureto
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.