Borrowing it
Nothing to install: this file belongs to Sanpelegrino/tableau-mcp-test. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sanpelegrino/tableau-mcp-test/main/.claude/skills/create-pr-from-commits/SKILL.mdgit clone --depth 1 https://github.com/Sanpelegrino/tableau-mcp-testWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sanpelegrino/tableau-mcp-test/create-pr-from-commits)<a href="https://agentmods.dev/skills/sanpelegrino/tableau-mcp-test/create-pr-from-commits"><img src="https://agentmods.dev/badge/skills/sanpelegrino/tableau-mcp-test/create-pr-from-commits/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sanpelegrino/tableau-mcp-test/create-pr-from-commits"><img src="https://agentmods.dev/badge/skills/sanpelegrino/tableau-mcp-test/create-pr-from-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.01969 |
| Opus 5 | $0.00017 | $0.00984 |
| Sonnet 5 | $0.00007 | $0.00394 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
create-pr-from-commits scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to create-pr-from-commits — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR from Commits
Overview
Automate pull request creation by extracting information from git commits and filling the repository's PR template. This eliminates manual repetition while ensuring PRs contain complete, accurate information.
When to Use
Use when:
- User asks to "create a PR"
- User says "make a pull request"
- User requests "submit this for review"
- You've created 2+ PRs in the session (proactively offer this workflow)
Don't use when:
- User wants to manually draft the PR description
- PR requires special context not in commits
- Repository has no PR template
Core Workflow
digraph pr_workflow {
"User requests PR" [shape=doublecircle];
"Gather git context" [shape=box];
"Find PR template" [shape=box];
"Analyze commits" [shape=box];
"Fill template" [shape=box];
"Create PR with gh pr create" [shape=box];
"Return PR URL" [shape=doublecircle];
"User requests PR" -> "Gather git context";
"Gather git context" -> "Find PR template";
"Find PR template" -> "Analyze commits";
"Analyze commits" -> "Fill template";
"Fill template" -> "Create PR with gh pr create";
"Create PR with gh pr create" -> "Return PR URL";
}
Implementation
Step 1: Prompt for GUS ID (Internal Contributors Only)
For internal Tableau contributors, ask for the GUS work item ID:
What is the GUS work item ID for this PR? (Format: W-12345678)
If you're an external contributor, press Enter to skip.
GUS ID format:
- Starts with
@W- - Followed by 8 digits
- Example:
@W-22802840
If the user provides just the number (e.g., "22802840"), prepend @W-.
If they provide "W-12345678", prepend @.
If no GUS ID provided: Continue without it - external contributors don't need GUS IDs.
Step 2: Gather Git Context (parallel)
Run these commands in parallel with Bash tool:
# Get all commits since main
git log main..HEAD --format="%h %s%n%b"
# Get full diff
git diff main...HEAD
# Get changed files
git diff main...HEAD --stat
# Check branch tracking
git branch -vv
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 292 lines · 35 tokens per session scan A aad536e565a5
create-pr-from-commits is a skill published in the GitHub repository Sanpelegrino/tableau-mcp-test (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,969 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-pr-from-commits, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.