Skip to content
Skills Library
Programming · Automation

git-commit-pr

/git-commit-pr

Guides local Git commit preparation and pull-request drafting with staged-diff and secret checks. Use when the user asks to commit changes, prepare a conventional commit, or draft a PR. When a dedicated GitHub publishing workflow is available, use it for pushing and opening the PR after these local checks.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/commit-check.sh, tests/commit-check.test.sh

What it does and when to use it

Guides local Git commit preparation and pull-request drafting with staged-diff and secret checks. Use when the user asks to commit changes, prepare a conventional commit, or draft a PR. When a dedicated GitHub publishing workflow is available, use it for pushing and opening the PR after these local checks.

Original author description

Guides local Git commit preparation and pull-request drafting with staged-diff and secret checks. Use when the user asks to commit changes, prepare a conventional commit, or draft a PR. When a dedicated GitHub publishing workflow is available, use it for pushing and opening the PR after these local checks.

How it works

  1. Pre-Commit Security Check
  2. Commit Workflow
  3. Commit Message Format
  4. PR Creation
  5. Security Rules
Original SKILL.md headings · 86 lines, 254 words
SKILL.md preview
---
name: git-commit-pr
description: Guides local Git commit preparation and pull-request drafting with staged-diff and secret checks. Use when the user asks to commit changes, prepare a conventional commit, or draft a PR. When a dedicated GitHub publishing workflow is available, use it for pushing and opening the PR after these local checks.
---

# Git Commit & PR Guide

Secure commits with consistent style.

## Pre-Commit Security Check

Before committing, scan for:
- API keys (`sk-`, `AKIA`, `ghp_`)
- Passwords in code
- `.env` files tracked by git
- Private keys (`.pem`, `.p12`)

Run the bundled check before committing. Resolve `COMMIT_CHECK_SKILL_DIR` to the
installed directory containing this `SKILL.md`; do not assume the target repository
contains the skill sources. The checker reports only affected file names, never the
matched secret values. Exit status 1 means a blocking finding and status 2 means the
Git data could not be inspected reliably.

```bash
"$COMMIT_CHECK_SKILL_DIR/scripts/commit-check.sh" staged
```

## Commit Workflow

### Step 1: Stage Changes
```bash
git add <specific-files>  # Prefer specific files
# Avoid: git add -A (may include secrets)
```

### Step 2: Review Staged
```bash
git diff --cached
"$COMMIT_CHECK_SKILL_DIR/scripts/commit-check.sh" staged
```

### Step 3: Commit
```bash
git commit -m "$(cat <<'EOF'
feat(auth): add JWT token validation

Implement token validation middleware with refresh logic.
EOF
)"
```

## Commit Message Format

```
<type>(<scope>): <subject>

<body>
```

Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`

## PR Creation

```bash
gh pr create --title "feat: add feature" --body "$(cat <<'EOF'
## Summary
- Change 1
- Change 2

## Test plan
- [ ] Unit tests pass
- [ ] Manual testing done
EOF
)"
```

## Security Rules

**NEVER commit:**
- `.env` files
- API keys/tokens
- Private keys
- Credentials

**Always check:**
```bash
git status  # No sensitive files staged
git diff --cached  # No secrets in diff
```
Files in this package (3)
  • SKILL.md 2 KB
  • scripts/commit-check.sh 19 KB
  • tests/commit-check.test.sh 18 KB

Versions

The database has no other skills named git-commit-pr.

Database snapshot: 13.11.2026 · package version 0620b44957c8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100git-commit-only
    Use when creating one local Git commit without pushing. Supports diff-based Conventional Commit type/scope/message generation, staged or requested change handling, segmented commit bodies for non-trivial changes, and safe commit-only workflows. Trigger for requests such as…
  • 100conventional-commit
    Write a Conventional Commits message for the staged changes. Use when the user asks to commit, write a commit message, or summarize staged changes for git.
  • 100git-commit
    Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
  • 100git-commit
    Commit staged changes with conventional commit message. Use when user says "commit changes", "commit this", "save my changes", or wants to create a git commit.
  • 100git-commit
    Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.
  • 100commit
    Stage and commit changes using Conventional Commits. Use when there are dirty/staged files to commit, the user says "commit", or before pushing a PR.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.