Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/git-github-flow

@9125e02
Run it yourself

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

Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/git-github-flow

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈362 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈183 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Use git-github-flow. Prepare a clean commit and PR description from my current diff. Do not push yet.
Use git-github-flow to respond to PR review comments. Preserve unrelated user changes.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The skill provides a structured workflow for managing Git branches, commits, and GitHub Pull Requests. It emphasizes security best practices such as avoiding secrets in commits and requiring human approval for destructive actions. No security risks were identified.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/git-github-flow