Install
$ agentstack add skill-ptdecker-kiss-skills-pr-announce ✓ 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 Review Announcement
Generate a short Slack post announcing that a PR is ready for review.
Step 1: Identify the PR
If the user provided a PR number as $ARGUMENTS, use that. Otherwise, determine the PR from the current branch:
gh pr view --json number,title,url,headRefName
Display the PR number, title, and URL. Ask the user to confirm this is the correct PR before proceeding.
Step 2: Gather PR context
Fetch the PR description and diff summary:
gh pr view --json number,title,body,url
gh pr diff --name-only
Read the PR body and the list of changed files to understand the scope and purpose of the changes.
Step 3: Write the announcement
Compose a message in this exact format:
PR # is ready for review.
The PR URL goes on its own line at the end so Slack auto-links it. Do not attempt Slack link markup (``) as it does not work when pasting into the message input box.
The summary paragraph should be 2-4 sentences. It should describe what the PR does and why, at a level appropriate for teammates who have not seen the code. Do not include file lists, line counts, or implementation details -- focus on the intent and impact of the change.
Step 4: Present and copy
Display the composed message to the user. Then copy it to the system clipboard:
echo "" | pbcopy
Let the user know the message has been copied to their clipboard and is ready to paste into Slack.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ptdecker
- Source: ptdecker/kiss-skills
- License: Unlicense
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.