القائمة
Generate a Slack recap message for a pull request and copy to clipboard. Use when a PR is ready to share with the team on Slack.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | slack-pr-recap |
| description | Generate a Slack recap message for a pull request and copy to clipboard. Use when a PR is ready to share with the team on Slack. |
| allowed-tools | Bash(gh pr:*), Bash(gh api:*), Bash(pbcopy), Bash(echo:*), Read, Glob, Grep |
Generate a concise, Slack-friendly recap message for the specified pull request.
Get the PR details:
gh pr view $ARGUMENT$ --json title,body,url,state,author,files,additions,deletions
Check for documentation changes to understand context:
gh pr diff $ARGUMENT$ -- '*.md' 'docs/*'
Focus on:
The additions, deletions, and files data is already available from the JSON output in step 1.
Based on the PR title, description, and changes, identify the type:
Create a message using Slack formatting:
*text* for bold<url|text> for links•Message Template:
🚀 *[PR Title]* (#[number])
📝 *What changed:*
• [Key change 1 - derived from docs/description]
• [Key change 2]
• [Key change 3 if needed]
🔧 *Type:* [Feature/Bugfix/Refactor/etc]
📁 *Scope:* [X] files changed (+[additions] -[deletions])
🔗 <[PR URL]|View PR>
Use pbcopy to automatically copy the message:
echo "[generated message]" | pbcopy
Display the message and confirm it's been copied to clipboard:
✅ Slack message copied to clipboard!
--- Message Preview ---
[show the message]
-----------------------
Ready to paste into Slack!
Create git commits from current changes using Conventional Commits format. Use when ready to commit staged or unstaged changes.
Generate a branch name from current changes and create it if on main. Use when starting new work and need a properly named feature branch.
Create a pull request from the current branch with quality checks. Use when changes are ready for review, after committing.
Interactive guide for creating new Claude skills with proper structure, frontmatter, and trigger conditions. Use when building a new skill, scaffolding a SKILL.md, or need guidance on skill best practices.
Run Prisma generate, lint (auto-fix), typecheck, and tests; iterate until clean, summarize results. Use when CI is failing or before pushing to verify the repo is clean.
Create a new GitHub issue for a feature, bug, or chore. Use when you have an idea, bug report, or task that needs a GitHub issue with analysis and solution options.