comment-hq
OrganizationComment.io engineering-workflow skills for any AI coding agent (Claude Code, Codex, Cursor) — plan, prototype, build, review, ship. npx skills add comment-hq/skills
Categories
Indexed Skills (16)
code-review
Run one evidence-focused, risk-scaled official code review on a pull request and post the result. Only invoke when explicitly requested as `$code-review` or `/code-review`, or when `ship` selects it as the sole official-review fallback.
comment-bug
Fix a bug end-to-end through a live Comment.io worklog comm — reproduce, write a regression test that fails first, fix, verify on the preview, and drive to a merge-ready PR, with the repro, root cause, and verification recorded as the decision history. Invoke explicitly as `$comment-bug` / `/comment-bug`, or when a task is a defect, regression, broken workflow, or user-visible failure to be reproduced and fixed with a watchable, steerable record. Replaces the retired bug skill. Works identically under Codex and Claude Code.
comment-dev
The front door for pragmatic engineering delivery through Comment.io. Talk to it about dev work in plain language and it picks the right path: shape a rough idea (`comment-spec`), build a defined feature (`comment-feature`), fix a defect (`comment-bug`), or try a fast change you'll validate later (`comment-prototype`). Invoke as `$comment-dev` / `/comment-dev`, or when someone describes coding work — "build / add / implement", "fix / it's broken", "let me try / quick tweak / show me", "should we / scope this" — without naming a specific path. When the user already named a specific skill, let that one fire directly. Works identically under Codex and Claude Code.
comment-feature
Deliver a defined feature pragmatically through a live Comment.io worklog: choose a direct PR or controlled lift, implement bounded deltas, use risk-scaled review receipts, validate the right boundary, and drive the result to a technically ready PR. Invoke as `$comment-feature` / `/comment-feature`, or when asked to build/add/implement a feature with a watchable, steerable record. Works identically under Codex and Claude Code.
comment-identity
Give this session a named, session-scoped Comment.io identity only when it is about to make a direct REST write without either a supplied per-doc token or a human-selected registered identity. Never invoke for Comment.io tools/MCP, browser actions, URL fetches, or reads: those routes carry their own identity and access, or are read-only. Runtime-generic (Claude Code, Codex, any shell agent). Mints one Ephemeral handle through a paired computer or owner ark_ key and degrades to anonymous when neither authority is available.
comment-init
Initialize or refresh a repo for the `comment-*` skill family. Two layers: (1) the **repo config the skills read** — the `AGENTS.md`/`CLAUDE.md` "Agent Skill Config" pointer plus `docs/DELIVERY.md` (topology, bounded review, and receipts) and `docs/TESTING.md` (focused iteration and final certification), inferred from the repo's build/test setup; and (2) the **architecture docs as comms** — one living "Architecture Overview" comm plus immutable per-decision ADRs in a Team Wiki folder. Idempotent — re-running reconciles existing files/comms instead of duplicating them. Trigger on "set up comment-init / the comment skills for this repo", "set up the testing config", "set up the architecture doc", "get my architecture", "document the architecture", "write an ADR", or "update the architecture overview". Works identically under Codex and Claude Code.
comment-prototype
Make a small or exploratory change FAST and show it, so you can look before committing to the merge-ready gate. Implements quickly, runs only a focused check (or none for a pure visual tweak), and surfaces the result in the real app — deliberately skipping the `review-loop` gate and the PR. When you like it, it promotes the work into `comment-feature` / `comment-bug` to harden and ship. Invoke as `$comment-prototype` / `/comment-prototype`, or when asked to "just try", "quickly tweak", "spike", "prototype", or "let me see X first". Works identically under Codex and Claude Code.
comment-spec
Shape a rough product idea into a crisp, proportionate spec through a live Comment.io comm, then hand it to comment-feature when build authority exists. Makes goal, acceptance, delivery topology, key risks, and out-of-scope clear; uses analytics, instrumentation, dashboards, concept mapping, and critic review only when the size of the product bet warrants them. Invoke as `$comment-spec` / `/comment-spec`, or when asked to spec, shape, scope, or design a feature before building. Works identically under Codex and Claude Code.
delivery-methodology
Choose and enforce a pragmatic engineering delivery topology: a direct PR for independently shippable work or a controlled lift branch for foundational work with unsafe intermediate states. Defines bounded SHA-delta reviews, risk-scaled reviewer counts, review receipts, lift freeze/promotion, and a technical-ready stopping point. Delivery skills call it before planning or shipping; invoke directly when deciding how a large change should reach main.
drive-plan
Drive a multi-phase implementation plan to completion through a Comment.io Plan/worklog or local Markdown plan. Uses phases as execution organization, not automatic gates; validates focused deltas, invokes bounded risk-scaled review at delivery-slice or changed-invariant boundaries, keeps the plan current, and steers only on real decisions. Invoke as `$drive-plan` / `/drive-plan`, or when asked to execute a phased plan autonomously. Works identically under Codex and Claude Code.
file-bug
Turn a user's report of something going wrong into a well-formed GitHub issue in the repo Claude is running in. Invoke explicitly as `$file-bug` or `/file-bug`, or when the user describes a defect, regression, broken behavior, confusing UX, error message, or a product idea and wants it captured as an issue/ticket — phrases like "file a bug", "open an issue for this", "log a ticket", "something's broken, write it up", or "track this idea". This skill investigates and writes the issue so the next person can understand AND reproduce the problem; it does NOT fix the bug or propose a fix.
review-loop
Review an explicit plan/code/PR SHA delta with a risk-scaled panel, fix one complete finding batch, validate the changed delta, and emit a durable review receipt. Defaults to one reviewer, adds targeted lenses for sensitive work, caps normal finding-bearing rounds, and avoids re-reading already certified branch history. Only invoke as `$review-loop` / `/review-loop`, or when a delivery skill calls it. Works identically under Codex and Claude Code.
ship
Drive a direct candidate, lift slice, or lift promotion through the right evidence and PR lifecycle. Runs exactly one official review for a direct/final candidate, consumes delta receipts for lift promotion, distinguishes technical readiness from human merge authority, and only queues/watches a merge when explicitly authorized. Invoke as `$ship` / `/ship`, or when asked to finish, land, merge, make a PR mergeable, or make it pristine. Works identically under Codex and Claude Code.
steer
Keep a human in the loop on a running task through a Comment.io comm. Poll the task comm for new @mentions and replies, fold human steering into the work mid-flight, and escalate by @mentioning a human and waiting when a decision shouldn't be made alone. Use during any long-running or autonomous task that has a worklog comm. Trigger when asked to "listen for steering", "check for comments", "escalate to a human", or whenever you need a human decision before continuing. Works identically under Codex and Claude Code.
worklog
Open and maintain a live Comment.io "worklog" comm as the shared working memory for one unit of work — a comm mirroring the plan, status, decisions, executive summary, and open questions, kept in sync as work proceeds. Other skills (comment-feature, comment-bug) call worklog to create and update the task comm. Use ONLY when explicitly asked to "open a worklog", "track this in a comm", or "give me a live status doc", or when a delivery skill (comment-feature / comment-bug) calls it — NOT automatically for routine local, read-only, or investigative work. Works identically under Codex and Claude Code.
next
Write a detailed handoff note for a future version of yourself covering progress and next steps. Only invoke when explicitly requested as `$next` or `/next`.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.