update-backlog-comments

Reviews and corrects your own comments on issue-tracking tickets for gaps, staleness, and readability.

Updated Dec 25, 2021
One-click install
npx skills add https://github.com/kotahashihama/dotfiles --skill update-backlog-comments-kotahashihama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-backlog-comments
Source: https://github.com/kotahashihama/dotfiles/tree/main/home/.claude/skills/update-backlog-comments
Command: npx skills add https://github.com/kotahashihama/dotfiles --skill update-backlog-comments-kotahashihama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Comments left on issue-tracking tickets drift out of date, accumulate unnecessary detail, or become hard to read, and unlike GitHub there are no format hooks or threads to catch problems automatically. This Skill audits your own posted comments against three axes—coverage gaps, divergence from reality, and readability—and fixes them safely. ## Core Features & Use Cases - Three-axis audit: Checks for missing or excess context comments (judged by whether artifacts fall outside the ticket's closing conditions), verifies factual claims against actual artifact states and diffs, and measures readability after excluding quotes and URLs. - Read-aware editing: Determines whether a comment has been read (reactions, later replies, elapsed time) and rewrites unread comments in place while appending corrections as new comments to read ones. - Safe operations: Verifies which update/delete operations the available tooling supports before acting, backs up content before irreversible deletions, and never rewrites tickets filed by other people. - Use Case: After finishing a multi-part ticket, ask the AI to review your comments on it; it will flag a stale claim about a missing configuration, trim an over-long comment, and add missing context for an artifact outside the acceptance criteria. ## Quick Start Review my comments on ticket PROJ-123 for gaps, staleness, and readability, and fix what needs fixing.

Frequently Asked Questions about update-backlog-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and update my old comments on backlog tickets?

Collect your own non-empty comments on the ticket, then audit them on three axes: coverage gaps relative to closing conditions, factual accuracy against current artifact states, and readability measured after excluding quotes and URLs. Rewrite unread comments in place and append corrections as new comments to ones already read.

How to decide whether to edit a comment or post a follow-up?

Check for evidence the comment was read: reactions, later comments from others, or significant elapsed time with active viewers. If no read evidence exists, rewrite in place; otherwise preserve the original and add a new comment. Purely factual corrections may be fixed even if read.

Why measure comment length after removing quotes and URLs?

Ticket text is often quoted verbatim, so raw measurement flags lines the writer is not responsible for. Excluding URLs, issue references, quoted passages, and formatting markers avoids false positives—in one real case, over-70-character lines dropped from 11 to 4.

Can I edit or delete comments posted via MCP or API?

It depends on the tooling and the provider's API—check which update and delete operations are actually available before starting. Deletion is irreversible, so back up the content first, and some document types may have no update endpoint at all.

When should I not rewrite a ticket comment?

Never rewrite the title or body of tickets filed by other people—leave corrections as comments instead. Also leave timestamped snapshot notes (like [memo] entries) alone, since they are meant to reflect a point in time.