smithery.ai

comment

Add an AI-generated comment to the current ClickUp task

First seen Apr 18, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,803 B
  • docs SUMMARY.md 70 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

/clickup:comment - Add Comment to Current Task

Purpose

Add a well-structured comment to the current ClickUp task. The comment is AI-generated based on your prompt and task context, then presented for confirmation before posting.

Usage

/clickup:comment <prompt>

Examples

/clickup:comment blocking - waiting for API credentials
/clickup:comment progress update - completed auth flow
/clickup:comment question - should we use OAuth or API keys?
/clickup:comment ready for review

Behavioral Flow

When this command is invoked:

  1. Detect Current Task:

- Get current git branch: git rev-parse --abbrev-ref HEAD - Extract task ID from branch name pattern: {type}/{task_id}-{title} - Example: fix/86bqy2f6j-payment-webhook → Task ID: 86bqy2f6j

  1. Fetch Task Context:

- Get task details from ClickUp for context (title, status, description)

  1. Gather Git Context (optional, for richer comments):

- Recent commits on branch: git log --oneline staging..HEAD - Files changed: git diff --stat staging...HEAD

  1. Generate Comment:

Based on the user's prompt, generate a well-structured markdown comment. Detect comment type from keywords:

Keyword Comment Type Icon
blocking, blocked, waiting Blocker ⏸️
progress, update, completed Progress Update 📊
question, help, clarify Question ❓
ready, done, finished Ready for Review ✅
issue, problem, bug Issue Found 🐛
  1. Show Preview for Confirmation:

``` 📋 Task: Fix payment webhook race condition 🌿 Branch: fix/86bqy2f6j-payment-webhook-race

📝 Generated Comment:


## ⏸️ Blocked

Reason: Waiting for API credentials

Current Progress: - Implemented core webhook handler - Added retry logic

Next Steps: Resume implementation once credentials are received.

Branch: fix/86bqy2f6j-payment-webhook-race


Post this comment to ClickUp? [Y/n] ```

  1. Post Comment (on confirmation):

``bash curl -X POST "https://api.clickup.com/api/v2/task/${TASKID}/comment" \ -H "Authorization: ${CLICKUPTOKEN}" \ -H "Content-Type: application/json" \ -d '{"comment_text": "..."}' ``

  1. Confirm Success:

`` ✅ Comment posted to ClickUp 🔗 View task: https://app.clickup.com/t/86bqy2f6j ``

Comment Templates

Blocker Comment

## ⏸️ Blocked

**Reason**: {user's reason}

**Current Progress**:
- {bullet points from git commits if available}

**Next Steps**: {what happens when unblocked}

**Branch**: `{branch-name}`

Progress Update

## 📊 Progress Update

**Completed**:
- {items from user prompt or git commits}

**In Progress**:
- {current work}

**Branch**: `{branch-name}`

Question

## ❓ Question

{user's question}

**Context**: {relevant task/branch info}

Ready for Review

## ✅ Ready for Review

**Summary**:
{brief summary of changes}

**Changes**:
- {list of changes from git}

**Branch**: `{branch-name}`

Error Handling

  • Not on a feature branch: "Not currently on a task branch. Use /clickup:work to start a task."
  • Task ID not found in branch: "Could not extract task ID from branch name."
  • Task not found in ClickUp: "Task {id} not found in ClickUp."
  • Comment cancelled: "Comment not posted."

Tool Coordination

  • Bash: Git commands and curl for ClickUp API
  • Read: Load .env file
  • AskUser: Confirm before posting comment

ARGUMENTS: $ARGUMENTS