How do I install the Git Commit Pr skill?

Run npx skillmds@latest add jiunbae/git-commit-pr 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 Commit Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commit Pr?

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 Commit Pr free to use?

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

Who published Git Commit Pr?

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

Git Commit Pr by jiunbae — Agent Skill

Name: Git Commit Pr
Rating: 4.2 (5 reviews)
Author: jiunbae

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.

jiunbae Updated Sep 10, 2026

File contents

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.

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

Commit Workflow

Step 1: Stage Changes

git add <specific-files>  # Prefer specific files
# Avoid: git add -A (may include secrets)

Step 2: Review Staged

git diff --cached
"$COMMIT_CHECK_SKILL_DIR/scripts/commit-check.sh" staged

Step 3: Commit

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

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:

git status  # No sensitive files staged
git diff --cached  # No secrets in diff

---name: git-commit-prdescription: 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 GuideSecure commits with consistent style.## Pre-Commit Security CheckBefore 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 theinstalled directory containing this `SKILL.md`; do not assume the target repositorycontains the skill sources. The checker reports only affected file names, never thematched secret values. Exit status 1 means a blocking finding and status 2 means theGit data could not be inspected reliably.```bash"$COMMIT_CHECK_SKILL_DIR/scripts/commit-check.sh" staged```## Commit Workflow### Step 1: Stage Changes```bashgit add <specific-files> # Prefer specific files# Avoid: git add -A (may include secrets)```### Step 2: Review Staged```bashgit diff --cached"$COMMIT_CHECK_SKILL_DIR/scripts/commit-check.sh" staged```### Step 3: Commit```bashgit commit -m "$(cat <<'EOF'feat(auth): add JWT token validationImplement token validation middleware with refresh logic.EOF)"```## Commit Message Format```<type>(<scope>): <subject><body>```Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`## PR Creation```bashgh pr create --title "feat: add feature" --body "$(cat <<'EOF'## Summary- Change 1- Change 2## Test plan- [ ] Unit tests pass- [ ] Manual testing doneEOF)"```## Security Rules**NEVER commit:**- `.env` files- API keys/tokens- Private keys- Credentials**Always check:**```bashgit status # No sensitive files stagedgit diff --cached # No secrets in diff```

Frequently asked questions