How do I install the Git Pr Workflow skill?

Run npx skillmds@latest add tomevault-io/git-pr-workflow-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Pr Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Pr Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Pr Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Pr Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Pr Workflow by tomevault-io — Agent Skill

Name: Git Pr Workflow
Author: tomevault-io

File contents

Git PR Workflow

Use this skill when the user asks to prepare changes for git, commit, push, and open a PR.

Required Sequence

Confirm branch context and inspect diffs.
Draft a descriptive commit message from actual code changes.
Run Go verification checks before staging/committing.
Only if checks pass: stage, commit, push.
Create PR with gh.

Do not skip or reorder these steps.

1. Branch and Diff Review

Run:

git branch --show-current
git status --short
git diff --stat
git diff
git diff --staged

Rules:

If branch is main or master, stop and ask the user for confirmation before committing.
If there are no changes, stop and report no-op.
Use the diff to understand what changed before writing commit/PR text.

2. Commit Message Construction

Create a commit message from the diff, not from guesswork.

Use Conventional Commits style:

Title format: <type>(<scope>): <summary>
Common types: feat, fix, refactor, docs, test, chore
Summary: imperative, specific, <= 72 chars
Optional body: short bullets describing key changes and rationale

Examples:

feat(discovery): implement parallel file walker with errgroup
fix(config): prevent panic on missing TOML key
refactor(pipeline): extract FileDescriptor to shared types
test(security): add redaction golden tests for AWS keys

3. Mandatory Pre-Commit Checks

Before git add or git commit, run:

./run_pipeline_checks.sh

If checks fail:

Attempt to fix the issue
Re-run checks

Rules:

Never commit when required checks fail.
The script runs the following checks in order (fail-fast):
- gofmt -l . — formatting check
- go vet ./... — vetting
- golangci-lint run — linting (skipped gracefully if not installed)
- go mod tidy + diff check — module hygiene
- go test -race -count=1 ./... — testing
- go build ./cmd/harvx/ — build (optional with --with-build flag)

4. Stage and Commit

Only after all checks pass:

git add <specific-files>
git commit -m "<title>" -m "<body>"

Prefer staging specific files over git add -A.

5. Push Branch

branch="$(git branch --show-current)"
git push --set-upstream origin "$branch" || git push origin "$branch"

6. Create PR

branch="$(git branch --show-current)"
base="$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name)"
gh pr create --base "$base" --head "$branch" --title "<pr-title>" --body "<pr-body>"

PR body should include:

## Summary
- [Key changes in bullets]

## Task Reference
- [T-XXX if applicable]

## Verification
- `go build` pass
- `go vet` pass
- `go test` pass

## Test Plan
- [How to verify the changes]

Final Report Format

Return:

Branch name
Commit title used
Verification check results
Push result
PR URL

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: git-pr-workflow-2description: Review branch diff, derive a descriptive commit message, run Go checks, then commit, push, and open a PR with gh. Use when this capability is needed.---# Git PR WorkflowUse this skill when the user asks to prepare changes for git, commit, push, and open a PR.## Required Sequence1. Confirm branch context and inspect diffs.2. Draft a descriptive commit message from actual code changes.3. Run Go verification checks before staging/committing.4. Only if checks pass: stage, commit, push.5. Create PR with `gh`.Do not skip or reorder these steps.## 1. Branch and Diff ReviewRun:```bashgit branch --show-currentgit status --shortgit diff --statgit diffgit diff --staged```Rules:- If branch is `main` or `master`, stop and ask the user for confirmation before committing.- If there are no changes, stop and report no-op.- Use the diff to understand what changed before writing commit/PR text.## 2. Commit Message ConstructionCreate a commit message from the diff, not from guesswork.Use Conventional Commits style:- Title format: `<type>(<scope>): <summary>`- Common types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`- Summary: imperative, specific, <= 72 chars- Optional body: short bullets describing key changes and rationaleExamples:- `feat(discovery): implement parallel file walker with errgroup`- `fix(config): prevent panic on missing TOML key`- `refactor(pipeline): extract FileDescriptor to shared types`- `test(security): add redaction golden tests for AWS keys`## 3. Mandatory Pre-Commit ChecksBefore `git add` or `git commit`, run:```bash./run_pipeline_checks.sh```If checks fail:1. Attempt to fix the issue2. Re-run checksRules:- Never commit when required checks fail.- The script runs the following checks in order (fail-fast): - `gofmt -l .` — formatting check - `go vet ./...` — vetting - `golangci-lint run` — linting (skipped gracefully if not installed) - `go mod tidy` + diff check — module hygiene - `go test -race -count=1 ./...` — testing - `go build ./cmd/harvx/` — build (optional with `--with-build` flag)## 4. Stage and CommitOnly after all checks pass:```bashgit add <specific-files>git commit -m "<title>" -m "<body>"```Prefer staging specific files over `git add -A`.## 5. Push Branch```bashbranch="$(git branch --show-current)"git push --set-upstream origin "$branch" || git push origin "$branch"```## 6. Create PR```bashbranch="$(git branch --show-current)"base="$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name)"gh pr create --base "$base" --head "$branch" --title "<pr-title>" --body "<pr-body>"```PR body should include:```markdown## Summary- [Key changes in bullets]## Task Reference- [T-XXX if applicable]## Verification- `go build` pass- `go vet` pass- `go test` pass## Test Plan- [How to verify the changes]```## Final Report FormatReturn:1. Branch name2. Commit title used3. Verification check results4. Push result5. PR URL---> Converted and distributed by [TomeVault](https://tomevault.io/claim/abdelazizmoustafa10m) — claim your Tome and manage your conversions.

Frequently asked questions

Git Pr Workflow