Is Comment Dev safe and trustworthy?

tashan scores Comment Dev on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Comment Dev?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Comment Dev?

2 GitHub contributors, source: comment-io/claude-code-plugin.

‹ The Index

Comment Dev

skill

- 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.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r comment-dev ~/.claude/skills/

Adoption: 1 repos
Upkeep: 80.0
Freshness: 95.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 2

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:comment-io/comment-dev

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-09 · scorer s5 · how · something wrong here?