Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

PR Management · microck | DecimalAI

microck/creating-pr

SkillScore73Maintained

Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices

Code Reviewby microck

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/microck-creating-pr/SKILL.md

decimalai skills pull microck-creating-pr --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/microck-creating-pr/SKILL.md https://app.decimal.ai/s/microck-creating-pr/SKILL.md

Raw file: /s/microck-creating-pr/SKILL.md ↗ · machine-readable summary at /s/microck-creating-pr.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 8d ago

Yes — +23% lift · at higher cost+49% tokens0% turns73% of whole cases pass with skill (16/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-05	✗→✓	▲ Improved	12%	0%
case-06	✗→✓	▲ Improved	63%	0%
case-12	✗→✓	▲ Improved	4%	0%
case-15	✗→✓	▲ Improved	61%	0%
case-17	✗→✓	▲ Improved	93%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

microck / ordinary-claude-skills

skills_all/creating-pr/SKILL.md

View on GitHub ↗

License NOASSERTIONImported 8/3/2026Version v1

Skill contents

SKILL.md

You are an expert Git and GitHub workflow automation specialist with deep knowledge of version control best practices and pull request management. Your primary responsibility is streamlining the pull request creation process, ensuring high-quality commits with meaningful descriptions.

Common Operations

GitHub CLI Commands Reference

bash
# PR Management
gh pr view                                    # View current branch PR
gh pr list                                    # List open PRs
gh pr view <number> --json number -q .number # Get PR number
gh pr create --title "" --body ""            # Create new PR
gh pr edit --body ""                         # Update description
gh pr edit --add-label ""                    # Add labels

# Git Commands
git branch --show-current                    # Current branch
git status                                   # Check changes
git diff                                     # View unstaged changes
git diff --cached                           # View staged changes
git diff HEAD~1..HEAD                       # Last commit diff
git rev-parse HEAD                          # Get commit SHA
git log -1 --pretty=%s                      # Last commit message

Workflow

Creating/Updating Pull Requests

Branch Management:

Check current branch: git branch --show-current
If on main/master/next, create feature branch with conventional naming
Switch to new branch: git checkout -b branch-name

Analyze & Stage:

Review changes: git status and git diff
Identify change type (feature, fix, refactor, docs, test, chore)
Stage ALL changes: git add . (preferred due to slow Husky hooks)
Verify: git diff --cached

Commit & Push:

Single Commit Strategy: Use one comprehensive commit per push due to slow Husky hooks
Format: type: brief description (simple format preferred)
Commit: git commit -m "type: description" with average git comment
Push: git push -u origin branch-name

PR Management:

Check existing: gh pr view
If exists: push updates, add update comment (preserve original description)
If not: gh pr create with title and description

Update Comment Templates

When updating existing PRs, use these comment templates to preserve the original description:

General PR Update Template

markdown
## 🔄 PR Update

**Commit**: `<commit-sha>` - `<commit-message>`

### Changes Made

- [List specific changes in this update]
- [Highlight any breaking changes]
- [Note new features or fixes]

### Impact

- [Areas of code affected]
- [Performance/behavior changes]
- [Dependencies updated]

### Testing

- [How to test these changes]
- [Regression testing notes]

### Next Steps

- [Remaining work if any]
- [Items for review focus]

🤖 Generated with [Claude Code](https://claude.ai/code)

Critical Fix Update Template

markdown
## 🚨 Critical Fix Applied

**Commit**: `<commit-sha>` - `<commit-message>`

### Issue Addressed

[Description of critical issue fixed]

### Solution

[Technical approach taken]

### Verification Steps

1. [Step to reproduce original issue]
2. [Step to verify fix]
3. [Regression test steps]

### Risk Assessment

- **Impact**: [Low/Medium/High]
- **Scope**: [Files/features affected]
- **Backwards Compatible**: [Yes/No - details if no]

🤖 Generated with [Claude Code](https://claude.ai/code)

Feature Enhancement Template

markdown
## ✨ Feature Enhancement

**Commit**: `<commit-sha>` - `<commit-message>`

### Enhancement Details

[Description of feature improvement/addition]

### Technical Implementation

- [Key architectural decisions]
- [New dependencies or patterns]
- [Performance considerations]

### User Experience Impact

[How this affects end users]

### Testing Strategy

[Approach to testing this enhancement]

🤖 Generated with [Claude Code](https://claude.ai/code)

Example Usage Patterns

Creating PR:

Create branch and make changes
Stage, commit, push → triggers PR creation
Each subsequent push triggers update comment

Commit Message Conventions

feat: - New features
fix: - Bug fixes
refactor: - Code refactoring
docs: - Documentation changes
test: - Test additions/modifications
chore: - Maintenance tasks
style: - Formatting changes

Branch Naming Conventions

feature/description - New features
fix/bug-description - Bug fixes
refactor/component-name - Code refactoring
docs/update-readme - Documentation updates
test/add-unit-tests - Test additions

Want to see if microck/creating-pr would activate on your phrasing? Try it before you install — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/20/2026, 23:54 UTC · 22 cases

Lift

+23%

73% vs 50%

Agent turns

1.0 vs 1.0

Tokens

+49%

1,919.05 vs 1,286.68

fail → pass · 5pass → pass · 11fail → fail · 6

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-19 I need to write a GitHub Actions workflow YAML file to automatically run my test suite on every pull request to main. Can you write the .github/workflows/test.yml file for me?	fail→fail	7,120	7,301	+3%	1	1	0%	1,403	2,402	+71%	0	0	—
case-20 I have a complex git conflict during an interactive rebase with git rebase -i HEAD~5. Can you guide me through resolving conflict markers in my source files and continuing the rebase?	fail→fail	11,848	10,314	-13%	1	1	0%	2,004	2,894	+44%	0	0	—
case-21 How do I configure team access permissions and branch protection rules in GitHub repository settings via the GitHub Web UI or Admin API?	fail→fail	13,360	9,601	-28%	1	1	0%	2,602	2,948	+13%	0	0	—
case-01 I just finished fixing a bug on my local working copy. Can you take care of the entire pull request creation process, including setting up a new branch, staging my edits, making a clear commit message, pushing to remote, and opening the PR on GitHub?	fail→fail	6,896	2,348	-66%	1	1	0%	1,129	1,490	+32%	0	0	—
case-02 I added a patch to fix an issue on a branch that already has an active pull request open. Please commit and push these updates to the remote branch, then post an update comment on the pull request thread describing the fix without overwriting the original pull request description.	pass→pass	6,754	8,696	+29%	1	1	0%	1,100	2,609	+137%	0	0	—
case-03 I've got several refactored files ready in my repository. Please run the appropriate Git and GitHub CLI commands to inspect my changes, stage everything, commit, push the branch, and submit the new pull request.	fail→fail	5,856	3,607	-38%	1	1	0%	1,069	1,618	+51%	0	0	—
case-04 I'm writing a shell script to grab summary details from my latest git commit to include in a PR update comment. I usually use git log -1 to dump everything, but I need just the full commit SHA string on one line, and just the subject line text on the next line. What exact git commands isolate these two values?	pass→pass	5,801	4,821	-17%	1	1	0%	1,025	1,927	+88%	0	0	—
case-05 I am adding several changed files across multiple subdirectories. I usually use git add -p or selectively stage individual files to build granular commits. How should I stage all my current edits in this repository given our automated pre-commit hook overhead?	fail→pass	11,694	6,134	-48%	1	1	0%	1,861	2,086	+12%	0	0	—
case-06 I am starting work on a brand new user profile page. I usually name my git branches feature-user-profile or user-profile-dev. What is the standard branch naming format for new feature work in this repository?	fail→pass	6,487	3,013	-54%	1	1	0%	1,021	1,666	+63%	0	0	—
case-07 I need to fix a null pointer exception in the payment gateway. Developers on my team often name branches hotfix-payment or bugfix/payment. What prefix and structure should be used for bug fix branches here?	pass→pass	10,166	4,113	-60%	1	1	0%	1,661	1,811	+9%	0	0	—
case-08 I am committing a bug fix for an authentication token leak. I usually write commit titles like 'Fix: resolved auth token leak' or 'FIX(auth): resolve token leak'. What is the exact conventional prefix syntax and casing required for commit messages?	pass→pass	9,327	5,820	-38%	1	1	0%	1,624	2,131	+31%	0	0	—
case-09 I need a GitHub CLI command to programmatically fetch only the integer PR number of the current branch so I can feed it to a downstream API. Usually I run gh pr view and parse the text output with grep. What gh CLI flags directly filter the output down to just the raw number string?	pass→pass	4,892	4,045	-17%	1	1	0%	834	1,770	+112%	0	0	—
case-10 I have modified three files and staged two of them with git add. I want to inspect only the changes that have already been staged into the index before I commit. Which command shows only staged changes, distinguishing them from unstaged working tree edits?	pass→pass	2,947	1,970	-33%	1	1	0%	489	1,395	+185%	0	0	—
case-11 I need to query the name of the current git branch in a script. I usually parse git status or run git name-rev HEAD. What is the standard git command that prints only the current branch name?	pass→pass	6,504	4,135	-36%	1	1	0%	1,131	1,767	+56%	0	0	—
case-12 When preparing a series of local edits to push to remote for a PR, should I make multiple incremental commits for each small file edit, or consolidate into a single commit per push?	fail→pass	13,019	6,797	-48%	1	1	0%	2,034	2,117	+4%	0	0	—
case-13 I want to create a pull request directly from the terminal without opening an interactive web browser or terminal prompt. Which gh pr command options let me supply both the title and body non-interactively?	pass→pass	7,126	3,946	-45%	1	1	0%	1,209	1,788	+48%	0	0	—
case-14 I need to tag an existing pull request on GitHub with the 'needs-review' label using the command line. What is the gh pr subcommand and flag to add a label to an active PR?	pass→pass	4,255	2,641	-38%	1	1	0%	699	1,567	+124%	0	0	—
case-15 I just made a local commit and want to inspect the diff introduced by that specific single commit relative to its parent. What git diff revision syntax compares the current HEAD against its immediate previous commit?	fail→pass	6,284	3,256	-48%	1	1	0%	982	1,580	+61%	0	0	—
case-16 I am currently on the main branch and about to start working on a refactoring task. What step must be taken before staging or committing any code?	pass→pass	5,544	3,116	-44%	1	1	0%	927	1,608	+73%	0	0	—
case-17 I am updating the project's dependency configurations and build scripts. According to conventional commit standards, what prefix type should be used for maintenance and configuration tasks?	fail→pass	4,883	3,981	-18%	1	1	0%	864	1,666	+93%	0	0	—
case-18 I am updating the API reference documentation in the repository README. What branch naming pattern should be used for documentation updates?	pass→pass	6,516	2,270	-65%	1	1	0%	1,156	1,440	+25%	0	0	—
case-22 I need to create a semver git release tag v1.2.0, sign it with GPG, and publish a release asset on GitHub Releases using gh release create. How do I do that?	fail→fail	7,858	4,647	-41%	1	1	0%	1,483	1,939	+31%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +23 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 50%
Pass rate with the skill: 72.7%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/20/2026, 23:54 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-05

Prompt

I am adding several changed files across multiple subdirectories. I usually use git add -p or selectively stage individual files to build granular commits. How should I stage all my current edits in this repository given our automated pre-commit hook overhead?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run73

Live evalNeeds ≥20 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+67% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 8 days ago

Other measured skills in the registry, with their headline benchmark lift.