Slash Command

/SKILL

Submits work for team review or approval: creates/updates review task, notifies reviewer via channel or DM, requests project state approval if specified.

developer-tools

automation

npx claudepluginhub cookjohn/teammcp

Details

Namespaceskills/submit-for-review/

Allowed Tools

mcp__teammcp__create_taskmcp__teammcp__update_taskmcp__teammcp__send_messagemcp__teammcp__send_dmmcp__teammcp__request_approvalmcp__teammcp__set_statemcp__teammcp__get_statemcp__teammcp__list_tasks

Prompt Preview

# Submit Work for Review

## Instructions

1. **Parse arguments**
   - Extract from `$ARGUMENTS`:
     - `title` — short description of what is being submitted
     - `reviewer` — the agent or role who should review (e.g., "CTO", "CEO", agent name)
     - `channel` (optional) — channel to post the review request in
     - `project_id` (optional) — associated project for state updates
   - If title or reviewer is missing, ask the user.

2. **Create or update the review task**
   - Call `list_tasks` to check if a review task for this work already exists.
   - If it exists, call `update_task` ...

Command Content

Other plugins with /SKILL

/team-update

689

Posts project updates to team chat, gathers and triages feedback via modes: update (full cycle), standup, check, feedback, plan.

1 tool

dev-tools

/team-delegate

32.9k

Displays task delegation dashboard showing unassigned tasks, member workloads, blocked tasks, and rebalancing suggestions. Also supports assigning tasks, sending messages, and rebalancing via flags.

agent-teams

/peer-review

Commits uncommitted work, creates PR if needed, and runs multi-agent peer review task hierarchy with remediation cycles and user approvals.

PACT

/SKILL

512

Configures Git user identity and project commit scopes: verifies name/email, initializes git-agent, validates scopes from .git-agent/config.yml, generates .claude/git.local.md.

haiku7 tools

git

/SKILL

512

Launches isolated code-context researcher agent to fetch repo/library context via DeepWiki, Context7, Exa, git clone, or all methods. Accepts repo URL/name and optional --method flag.

code-context

/SKILL

512

Creates a GitHub pull request with automated quality validation, security scanning, issue linking, and compliance checks. Accepts optional description or issue reference.

3 tools

github

Stats

Stars37

Forks3

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Submit Work for Review ## Instructions 1. **Parse arguments** - Extract from `$ARGUMENTS`: - `title` — short description of what is being submitted - `reviewer` — the agent or role who should review (e.g., "CTO", "CEO", agent name) - `channel` (optional) — channel to post the review request in - `project_id` (optional) — associated project for state updates - If title or reviewer is missing, ask the user. 2. **Create or update the review task** - Call `list_tasks` to check if a review task for this work already exists. - If it exists, call `update_task` ...

Submit Work for Review

Instructions

Parse arguments

Extract from $ARGUMENTS:
- title — short description of what is being submitted
- reviewer — the agent or role who should review (e.g., "CTO", "CEO", agent name)
- channel (optional) — channel to post the review request in
- project_id (optional) — associated project for state updates
If title or reviewer is missing, ask the user.

Create or update the review task

Call list_tasks to check if a review task for this work already exists.
If it exists, call update_task to set its status to "in-review" and update the description.
If it does not exist, call create_task with:
- Title: the provided title
- Status: "in-review"
- Assignee: the reviewer
- Description: summary of what is being submitted and what to review

Notify the reviewer

If a channel is specified, call send_message to the channel with the review request, including:
- What is being submitted
- Task ID for reference
- What kind of feedback is expected
Always also call send_dm to the reviewer directly with the review details.

Request state approval (if applicable)

If a project_id is provided:
- Call request_approval to request a state transition (e.g., status from "in-progress" to "in-review").
- This notifies the state owner that approval is needed.

Confirm submission

Output a summary:
- Task ID created/updated
- Reviewer notified
- Approval requested (if applicable)
- Next steps (wait for reviewer feedback)

$ARGUMENTS

/submit-for-review "<title>" <reviewer>

/submit-for-review "<title>" <reviewer> --channel <channel>

/submit-for-review "<title>" <reviewer> --project <project_id>

Example: /submit-for-review "API authentication module" CEO --channel general --project proj-123

Submit Work for Review

Instructions

Parse arguments
- Extract from $ARGUMENTS:
  - title — short description of what is being submitted
  - reviewer — the agent or role who should review (e.g., "CTO", "CEO", agent name)
  - channel (optional) — channel to post the review request in
  - project_id (optional) — associated project for state updates
- If title or reviewer is missing, ask the user.
Create or update the review task
- Call list_tasks to check if a review task for this work already exists.
- If it exists, call update_task to set its status to "in-review" and update the description.
- If it does not exist, call create_task with:
  - Title: the provided title
  - Status: "in-review"
  - Assignee: the reviewer
  - Description: summary of what is being submitted and what to review
Notify the reviewer
- If a channel is specified, call send_message to the channel with the review request, including:
  - What is being submitted
  - Task ID for reference
  - What kind of feedback is expected
- Always also call send_dm to the reviewer directly with the review details.
Request state approval (if applicable)
- If a project_id is provided:
  - Call request_approval to request a state transition (e.g., status from "in-progress" to "in-review").
  - This notifies the state owner that approval is needed.
Confirm submission
- Output a summary:
  - Task ID created/updated
  - Reviewer notified
  - Approval requested (if applicable)
  - Next steps (wait for reviewer feedback)

$ARGUMENTS

/submit-for-review "<title>" <reviewer>
/submit-for-review "<title>" <reviewer> --channel <channel>
/submit-for-review "<title>" <reviewer> --project <project_id>
Example: /submit-for-review "API authentication module" CEO --channel general --project proj-123