AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Workflow

skill-dominikwozniak-claude-kit-git-workflow · by dominikwozniak

>-

No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-dominikwozniak-claude-kit-git-workflow

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-dominikwozniak-claude-kit-git-workflow)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
Archived

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Git Workflow? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

git-workflow

One skill, all git ops. Configurable via CLAUDE.local.md.

Step 0: read project conventions

Before any operation, read CLAUDE.local.md (repo root) if it exists. Look for a ## Git conventions block. Use those values to override the defaults below. Examples of overridable values: commit format, default branch, branch naming, Co-Authored-By inclusion, PR title format.

If no CLAUDE.local.md or no ## Git conventions block, use the defaults documented in each section.

Operations

commit

Defaults:

  • Format: [TICKET-XXX] type: description if current branch matches ^[A-Z]+-\d+, else type: description
  • Subject follows Conventional Commits (feat/fix/refactor/docs/test/chore/perf/ci/build/style/revert)
  • Subject: imperative, lowercase, no period, ≤72 chars
  • Body: explain what + why for non-trivial changes; skip for trivial
  • NO Co-Authored-By trailer
  • NO "Generated with Claude Code" or any attribution footer
  • One logical change per commit — when session work spans multiple concerns, split

Workflow:

  1. git status --short — see all changes
  2. Classify files: session work (created/edited this conversation) vs pre-existing
  3. Stage session work by name: git add path1 path2. Never git add . or git add -A unless explicitly asked
  4. Sensitive files (.env, credentials, API keys): warn and exclude
  5. git diff --staged — review
  6. Extract ticket key from branch name: git branch --show-current | grep -oE '^[A-Z]+-[0-9]+'
  7. Generate subject. If ticket key found, prefix [KEY]
  8. Commit via heredoc:
git commit -m "$(cat /dev/null`
4. If no upstream, `git push -u origin "$(git branch --show-current)"`. Else `git push`
5. Report result

### PR (`open PR`, `create pull request`)

**Defaults:**

- Title: same format as commit subject (`[TICKET-XXX] type: description`)
- Body: summary + test plan from commits since base branch
- **NO** "Generated with Claude Code" footer
- Created via `gh pr create` — never the web UI

**Workflow:**

1. Push branch first if not pushed (see push section)
2. Determine base branch (default from CLAUDE.local.md or `git symbolic-ref --short refs/remotes/origin/HEAD`)
3. Generate body:

```markdown
## Summary

- 

## Test plan

- [ ] 
- [ ] 
  1. Title format: [KEY] type: description if ticket present in branch, else type: description
  2. Create:
gh pr create --title "..." --body "$(cat 

If conflicts: report them, do NOT auto-resolve, let user decide.

branch (new branch, switch branch)

Defaults:

  • Use git switch -c (not git checkout -b)
  • Branch name: prompt for ticket key + slug if not provided

Workflow:

git switch -c -
# or
git switch -c /

stash (stash my work)

Defaults:

  • Always with a message: git stash push -m "..."
  • Never bare git stash

Workflow:

git stash push -m ""

Notes

  • All defaults assume block-dangerous-git.sh hook is installed via bootstrap-workflow. If absent, manually refuse the same patterns (force-push, hard-reset, etc.).
  • If the project has a PR template at .github/PULL_REQUEST_TEMPLATE.md, use it as the body skeleton instead of the generic summary/test-plan format above.

Source & license

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

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

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.