Install
$ agentstack add skill-dominikwozniak-claude-kit-git-workflow ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →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: descriptionif current branch matches^[A-Z]+-\d+, elsetype: 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-Bytrailer - NO "Generated with Claude Code" or any attribution footer
- One logical change per commit — when session work spans multiple concerns, split
Workflow:
git status --short— see all changes- Classify files: session work (created/edited this conversation) vs pre-existing
- Stage session work by name:
git add path1 path2. Nevergit add .orgit add -Aunless explicitly asked - Sensitive files (
.env, credentials, API keys): warn and exclude git diff --staged— review- Extract ticket key from branch name:
git branch --show-current | grep -oE '^[A-Z]+-[0-9]+' - Generate subject. If ticket key found, prefix
[KEY] - 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
- [ ]
- [ ]
- Title format:
[KEY] type: descriptionif ticket present in branch, elsetype: description - 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(notgit 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.shhook is installed viabootstrap-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.
- Author: dominikwozniak
- Source: dominikwozniak/claude-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.