comment
$
npx mdskill add TheBushidoCollective/han/commentAdds comments to ClickUp tasks via slash commands, prompting for text if needed.
- Helps users annotate tasks with notes, updates, or markdown-formatted content.
- Integrates with ClickUp's API to post comments to specified task IDs.
- Executes based on user-provided task identifiers and optional comment input.
- Displays confirmation messages with task URLs and supports markdown formatting tips.
SKILL.md
.github/skills/commentView on GitHub ↗
---
name: comment
description: Add a comment to a ClickUp task
---
# comment
## Name
clickup:comment - Add a comment to a ClickUp task
## Synopsis
```
/comment [arguments]
```
## Description
Add a comment to a ClickUp task
## Implementation
Add a comment to a ClickUp task.
**Usage**: `/comment #ABC123 [optional: comment text]` or `/comment ABC123 [optional: comment text]`
If comment text is not provided, prompt for it with support for multi-line input.
Use `clickup_add_comment` to add the comment.
**Display Format**:
```
💬 Adding comment to #ABC123
Comment:
{comment text}
Posted successfully!
View task: {task URL}
```
Support markdown formatting in comments:
- Bold: **text**
- Italic: *text*
- Code: `code`
- Code blocks: ```language
- Lists
- Links
- Task mentions: #taskid
Provide formatting tips if user is writing a longer comment.
Optionally ask if they want to notify all task followers.
More from TheBushidoCollective/han
- absinthe-resolversUse when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.
- absinthe-schemaUse when designing GraphQL schemas with Absinthe. Covers type definitions, interfaces, unions, enums, and schema organization patterns.
- absinthe-subscriptionsUse when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
- act-docker-setupUse when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.
- act-local-testingUse when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
- act-workflow-syntaxUse when creating or modifying GitHub Actions workflow files. Provides guidance on workflow syntax, triggers, jobs, steps, and expressions for creating valid GitHub Actions workflows that can be tested locally with act.
- ameba-configurationUse when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
- ameba-custom-rulesUse when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
- ameba-integrationUse when integrating Ameba into development workflows including CI/CD pipelines, pre-commit hooks, GitHub Actions, and automated code review processes.
- analyze-performanceAnalyze performance metrics and identify slow transactions in Sentry