create-pr-github-git 100/100

Is create-pr-github-git safe to install?

SaferSkills independently audited create-pr-github-git (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/create-pr-github-git/SKILL.md · 1 file

skills/create-pr-github-git/SKILL.md1.7 KB · Markdown

description: Create a GitHub pull request from the current branch, deriving the title and description from the branch's git history.

disable-model-invocation: true

Create a GitHub pull request from the current branch, deriving the title and description from the branch's git history.

Steps:

Check that gh is installed and authenticated by running gh auth status. If not, tell the user and stop.
Get the repo's default branch: gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'. Use this as the base for all comparisons below (referred to as <base>).
Push the current branch to the remote if needed:

Run git rev-parse --abbrev-ref --symbolic-full-name @{upstream} to check if an upstream is set.
If no upstream is set, run git push -u origin HEAD to push and set tracking.
If an upstream is set, run git push to make sure the remote is up to date.

Run git log --oneline <base>..HEAD to list commits on this branch.
Run git diff <base>...HEAD --stat to understand what changed.
Derive a PR title (imperative tense, under 72 chars) and description from the commits and diff:

What changed (2-4 sentences, plain English)
Why it was needed if inferrable
Notable implementation details as bullet points (optional)
No filler like "This PR..." or vague words without specifics

Check if a PR already exists for this branch: gh pr view --json url,number 2>/dev/null.

If no PR exists, run gh pr create --title "<title>" --body "<description>" to open one. Append any user-provided flags from $ARGUMENTS.
If a PR already exists, run gh pr edit --title "<title>" --body "<description>" to update it.

Print the PR URL.

$ARGUMENTS

create-pr-github-git— agent skill

Is create-pr-github-git safe to install?

Audit the pieces. Scan the whole. Decide.