task-comment SKILL.md skillA
task-comment from bluestep-systems/bluestep-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bluestep-systems/bluestep-ai/task-comment@git:20261103.5c82982Pins git:20261103.5c82982 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bluestep-systems/bluestep-ai
- Path
plugins/bluestep-tools/skills/task-comment/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261103.5c82982, committed Nov 3, 2026
- Size
- 3,545 bytes
- Repository stars
- 3
- License
- none declared
Draft a standardized implementation comment for a ClickUp task after a fix or feature is shipped. Handles both org-propagated (component-based) and direct (code-only) changes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /task-comment — Draft a ClickUp implementation comment ## Steps 1. **Ask the user to paste the ClickUp task link or ID.** - Use the ClickUp MCP to fetch the task (`clickup_get_task`) and read its name, description, list, and status. 2. **Infer the change type from the task name prefix:** - Starts with `Bug -` or `Bug —` → type = **Fix** - Starts with `Feature -` or `Feature —` → type = **Feature** - Anything else → type = **Update** 3. **Derive the summary** from the task name and description — one sentence capturing what the bug/issue/feature was. Do not ask the user for this. 4. **Ask one question:** > Does this change need to be propagated to other orgs? (yes / no) 5. **Collect the remaining details based on the answer:** **If yes (propagated — component change):** - Component name (e.g. `Audits`, `Appointments`) - Affected file(s): path(s) relative to the component (e.g. `draft/scripts/utils/entryHelper.ts`) - Orgs deployed to (comma-separated list) - What changed and why (free-form: 1–4 sentences OR a short bullet list) **If no (direct — code/API/formula fix):** - What changed mechanically (1–3 sentences OR a short bullet list) …
Read the whole file at its exact version.
How to install
mdr add bluestep-systems/bluestep-ai/task-comment@sha256:a05d4100221539b7The line at the top of this page pins the label git:20261103.5c82982, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5eh46s2fdcikqu22)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3545 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bluestep-systems/bluestep-ai · 3 stars · license none declared · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5eh46s2fdcikqu22 GET https://markdownregistry.com/api/v1/resolve?ref=bluestep-systems/bluestep-ai/task-comment GET https://markdownregistry.com/api/v1/blob/a05d4100221539b769bd698a65a5cd25b63f0791c0f362c9192950a18ac636c3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.