القائمة
Send a notification to the
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
End-to-end workflow for building out a ticket — write code, open a PR, watch it for CI, code review, and QA, then address feedback, push fixes, and converse with QA via /qa-manager comments. Use when the user wants to take a ticket through the full Cosmos PR review loop, drive a PR to green, or process reviewer/QA feedback on an open PR.
Autofix common code-quality issues by running a pipeline of focused sub-agents (one-class-per-file, etc.). Use when the user wants to clean up code smells, normalize file structure, or run autofix on a set of files.
Show a dashboard of actionable PRs you've authored. Use when the user wants to see their open PRs, check PR status, review their PR pipeline, or find PRs that need attention.
Review and interactively address PR comments. Use when the user wants to review PR feedback, go through PR comments, or address reviewer requests on a pull request.
This skill should be used proactively whenever Claude needs to interact with, test, validate, verify, or observe a terminal user interface (TUI). This includes after writing TUI code and wanting to confirm it works, when debugging TUI behavior, when asked to verify UI changes, when running end-to-end validation of a TUI application, or any time Claude determines that launching and driving a TUI programmatically would help complete the task. Do not wait for the user to ask — use this skill autonomously whenever TUI interaction would validate work or answer questions.
Create a pull request from the current branch. Use when the user wants to open a PR, create a pull request, or push their branch up for review.
| name | bb-slack:notify |
| description | Send a notification to the |
| argument-hint | [message] |
Send a notification message to the #bb-claude channel so the user gets alerted.
$ARGUMENTS — The message to send. If empty, summarize what was just completed.
Every message MUST start with the header line:
⚡ *Claude Code* ⚡
Followed by the notification content on the next line.
⚡ *Claude Code* ⚡
Task complete: Refactored auth middleware and all tests pass.
⚡ *Claude Code* ⚡ header on the first line.$ARGUMENTS is provided, use it as the message body. Otherwise, summarize the most recent completed work.C0AQ0PW4VAL using the Slack MCP slack_send_message tool.