review-markdown-comments
Reply to, resolve, or reopen Hubble review comments stored as CriticMarkup in Markdown files. Use when asked to address a Hubble review comment.
How do I install this agent skill?
npx skills add https://github.com/bholmesdev/hubble-skills --skill review-markdown-commentsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill allows an agent to manage and reply to review comments stored in Markdown files. It uses structural delimiters to identify comments and update their metadata.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Review Markdown Comments
Work directly on the Markdown file named by the user.
Comment format
Hubble stores review state in the Markdown body using this portable subset:
{==anchored text==}{>>comment body<<}{#c1}
{++suggested insertion++}
{--suggested deletion--}
{~~original text~>replacement text~~}
Thread state may follow a comment anchor as an HTML comment holding raw JSON.
It is not URI-encoded; Hubble parses it with JSON.parse directly, so an
encoded payload fails to parse and renders as literal text in the note:
<!-- hubble-review:{"v":1,"replies":[],"resolved":false}-->
Hubble uses v, replies, and resolved; other top-level keys are allowed.
Always write "v": 1. Escape any -- inside the JSON as \u002d\u002d,
since a literal -- terminates the HTML comment early. A reply has this
shape:
{
"id": "r1",
"body": "Agent response",
"author": "agent",
"createdAt": "2026-01-01T00:00:00.000Z"
}
Review markers inside inline code or fenced code are literal text, not comments.
Address a comment
- Read the complete file. Locate the requested compact id, such as
{#c7}; if the user gives only anchored text, locate the exact CriticMarkup anchor instead. Confirm the anchored text and comment body match the user's request. If the id or exact anchor is absent or ambiguous, stop and report the ambiguity. - Parse the JSON metadata immediately following that logical comment. If it is absent, start from an empty object. If it is malformed, stop rather than overwrite it.
- Round-trip the metadata: mutate only the reply list and
resolved, then re-serialize the complete object — every other key and every existing reply survives unchanged. Replies are append-only: add a reply with the next unusedrNid,author: "agent", the response body, and the current UTC time as an ISO-8601createdAt. - Set
resolved: trueonly when the user's request has actually been addressed. For an explicit reopen request, setresolved: false. Acknowledgements, tests, questions, and partial work leave itfalse. - Write the metadata block immediately after the comment's
{#cN}marker (see Fragmented anchors). Keep the anchored text byte-for-byte unchanged, along with the comment body, CriticMarkup delimiters, suggested edits, and all unrelated Markdown.
Fragmented anchors
One logical comment id may appear in multiple CriticMarkup fragments. The final fragment is authoritative: keep every marker, keep a single metadata block, and place it after the final fragment — moving it there if it currently follows an earlier fragment. Report the fragmentation if it may affect the user's formatting.
Validation
After editing:
- Re-read the file and confirm the requested id and exact anchored text are still present.
- Parse the metadata after the final fragment and verify it is valid JSON,
the new reply is the final reply, the old replies and other keys
round-tripped, and
resolvedhas the intended value. Confirm the note renders the comment rather than showing the raw block as text. Check that every{==,==},{>>,<<}, and{#you touched belongs to a complete{==…==}{>>…<<}{#cN}span on one line; a stray delimiter means the span will not parse and shows as raw text in the note. - Check the surrounding Markdown for accidental changes: inspect
git diff -- <file>for a tracked file, or compare the before and after text for an ignored/generated file. - Report the reply you left and whether you resolved the comment.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/bholmesdev/hubble-skills/review-markdown-comments">View review-markdown-comments on skillZs</a>