Snap pr
SNAP — agent skills for smart models that ship real software.
npx -y skills add sadiksaifi/skills --skill snap-prAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create or update a GitHub pull request from the current branch's committed work. Use when the user wants to open a PR, refresh the current branch PR, push committed work, or prepare a reviewer-ready PR title and body.
SKILL.md
1.6 KB, as published. Nobody here has run it
Invocation
Syntax: /skill:snap-pr [update]
Args
| Key | Values | Default | Notes |
|---|---|---|---|
help | bool | false | show usage |
update | bool | false | update the current branch PR instead of creating one |
Create or update a GitHub pull request from the current branch's committed work.
Process
-
Inspect git state: current branch, default branch, working tree, unpushed commits, and current-branch PR.
-
Choose mode:
- default: create a PR; if one already exists, stop and ask whether to update
update: update the current-branch PR; if none exists, stop
-
Ensure branch truth:
- uncommitted relevant work: ask whether to commit it
- unpushed commits: push them
-
Write PR:
- create: use session context first; inspect
base...HEADonly when context is missing - update: inspect
base...HEAD - use commits as evidence only; do not list commit subjects, hashes, or counts in the PR body unless the user explicitly asks
- describe
## Changesby user-visible behavior, subsystem, or review area rather than by commit chronology - use the repo PR template when present; always include the QA section from
references/template.md; if no repo PR template exists, usereferences/template.mdas the fallback template
- create: use session context first; inspect
-
Publish:
- create or update the PR
- show the PR URL