Guides branching, committing, pushing, and stacked PR workflows in Git repositories.
npx skills add https://github.com/nejcm/agents --skill git-workflow-nejcm
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/nejcm/agents/tree/main/skills/git-workflow Command: npx skills add https://github.com/nejcm/agents --skill git-workflow-nejcm
gh stack GitHub CLI extension to build, submit, sync, and merge chains of small reviewable PRs for large or dependent changes. - Structured Results and Safety Rules: Returns JSON success/error payloads and enforces guardrails like never force-pushing main and never committing credentials. - Use Case: You have a large feature split into auth, API, and frontend layers. Use this Skill to create a stacked branch chain with gh stack, submit review-ready PRs, and keep each layer rebased and mergeable. ## Quick Start Ask the agent to create a feature branch, commit the current changes with a conventional commit message, and push it for review.High-intent search queries and answers about installing and using this skill.
Install the gh-stack extension with gh extension install github/gh-stack, then run gh stack init, gh stack add for each layer, and gh stack submit --auto --open to push branches and open review-ready PRs. Each PR is based on the branch below it in the chain.
Start by running git status --porcelain and git diff --stat to identify staged, unstaged, and untracked files. Stage only the intended files with git add, review the staged diff with git diff --cached, then commit with a conventional message.
It uses a conventional format of type, subject, body, and footer. Types include feat, fix, refactor, test, docs, and chore, with imperative subjects and issue links in the footer.
No. The workflow explicitly forbids force-pushing main or master and requires resolving conflicts and running the full test suite before any push. Destructive Git commands require explicit approval.
Drafts happen when the --open flag is omitted. Always run gh stack submit --auto --open, since drafts skip CI and review automation. Also pass non-interactive flags like --json and --yes to avoid blocking TTY prompts.
Use stacked PRs for large or dependent changes that should land as a chain of small reviewable PRs rather than one big diff. Stacks are strictly linear, so use a separate stack per independent line of work.
beam-ai-teamAutomate and guide Git operations for Nexus repositories.
bravrosCreates GitHub pull requests with base branch detection and review handoff.
ArthTech-AIValidate changes with QA checks, commit, push, and open a GitHub pull request.
learntocloudManage stacked branches and dependent pull requests with the gh-stack GitHub CLI extension.