Install
$ agentstack add skill-rikdc-ai-skills-pr ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PR - GitHub Pull Request Creation
Creates a draft pull request with a conventional-commit title and a short description of what the branch actually changes.
Workflow
- Validate:
gh auth status, current branch, uncommitted changes. - Read the branch:
git log ..HEADandgit diff ...HEAD—
the description covers exactly this, nothing more.
- Write the body: use
.github/pull_request_template.mdif present,
otherwise the sections below.
- Create:
gh pr create --draft --title "(): " --body-file --base main
Title Rules
- Conventional commit format:
():. - No emoji. The title is plain text.
- Under 70 characters, imperative mood, no trailing period.
- For a single-commit PR, reuse that commit's subject.
Examples:
feat(auth): add session refresh endpointfix(scanner): match patterns case-insensitivelydocs: document the scanner exit codes
Body Rules
Keep it succinct. The PR body describes the commits on the branch and nothing else.
- Summary: one to three sentences. What changed and why. No restating the
title, no background essay.
- Changes: one bullet per meaningful change, one line each. Group trivial
edits rather than listing every file. Under six bullets for a normal PR — if it needs more, the PR is probably too large.
- Testing: one line stating what was run (
make test,go test ./...) and
the result. Say so plainly if nothing was run.
- Drop any template section that has nothing real to say.
- No emoji, no headings beyond the template's, no "Notes for reviewers",
"Future work", "Impact", or risk-assessment sections unless asked.
- Do not claim behaviour you have not verified.
Default body when there is no template:
## Summary
## Changes
-
-
## Testing
Example body:
## Summary
Pattern matching in the MCP scanner was case-sensitive, so uppercase AWS keys
passed the scan. Matching is now case-insensitive.
## Changes
- Add `-i` to the pattern grep in `mcp-security-scanner.sh`
- Cover uppercase keys in `tests/test-scanner.sh`
## Testing
`make test` — all suites pass.
Common Actions
gh pr ready # draft to ready
gh pr edit --add-reviewer user1,user2 # add reviewers
gh pr status # check status
Error Handling
- Missing
gh: prompt to install. - Not authenticated: run
gh auth statusand prompt to log in. - Missing PR template: use the default body above; do not create the template
file unless asked.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rikdc
- Source: rikdc/ai-skills
- License: MPL-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.