comment-mode
Granular feedback on drafts without rewriting. Generates highlighted HTML with click-to-reveal inline comments. Use when user says "comment on this", "leave comments on", "give feedback on", or asks for feedback on a draft. Supports multiple lenses—editor feedback, POV simulation
Supply asset profile
Coding and developer agents
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Cursor + Browser agents
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add shipshitdev/skills --skill comment-mode
Maintenance
fresh
2d since push
Risk
Needs review
License is unclear
GitHub quality
33
57/100 Quality · 66/100 Trust
Coverage tags
Review notes
License is unclear · Permission surface may require sandboxing
Agent adoption scorecard
Trust, audit, and install readiness at a glance
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Do not auto-installTrust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Human review before install
Choose a stronger alternative or inspect the source manually before any install attempt.
Stars
33 GitHub stars
Repo activity
33 stars, 3 forks
Maintenance
2d since push
License
Unknown
Install
npx skills add shipshitdev/skills --skill comment-mode
Install safety
standard package or runtime install path
Permission surface
shell or command execution, filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Review before production
- Repository license detected as Unknown, though plugin.json declares MIT. This mismatch may cause compliance ambiguity.
- Financial research output is not financial advice; require human review before any live investment decision.
- License is unclear
- Low GitHub adoption signal
Install readiness
Install path available
- Install path is available
- Repository evidence is available
- License is unclear
- No Agent Proven outcome evidence yet
Agent-readable metadata
Machine-readable decision data for this skill.
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
- GitHub automation workflows
- Claude Code teams
- builders willing to evaluate younger projects
- Inspect repository metadata
Suited agents
Install decision
- Command
- npx skills add shipshitdev/skills --skill comment-mode
- Policy
- review
- Human review
- yes
Trust and risk
- Trust
- 58/100
- Audit
- 71/100
- Risk level
- Needs review
Outcome loop
- Endpoint
- /api/agent/outcome
- Event ID
- resolve
- Outcomes
- 5
Install command
npx skills add shipshitdev/skills --skill comment-modeDo not use when
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- Repository license detected as Unknown, though plugin.json declares MIT. This mismatch may cause compliance ambiguity.
- No OpenAgentSkill engagement data yet
Alternative
Code Review
168.6K Stars
npx skills add mattpocock/skills --skill code-review
Alternative
Grill With Docs
164.7K Stars
npx skills add mattpocock/skills --skill grill-with-docs
Alternative
To Spec
164.7K Stars
npx skills add mattpocock/skills --skill to-spec
Alternative
To Tickets
176.7K Stars
npx skills add mattpocock/skills --skill to-tickets
Agent safety v2
39/100 · Avoid automatic install
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Shell or command execution
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Browser automation
Skill may drive a browser or interact with web pages.
medium
Network access
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Filesystem access
Skill may read or write project files, documents, generated artifacts, or local workspace state.
- High-risk permission hints: Shell or command execution
- License is unclear
Install targets
Install this skill in your agent workflow
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
OpenAgentSkill CLI
Resolve policy, run the source installer safely, and report a verified install receipt.
$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install shipshitdev-comment-modeAgent resolve plan
Let an agent verify fit before installing.
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20comment-mode%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20comment-mode%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/shipshitdev-comment-mode/install
Agent should check
- Task fit and alternatives from Resolve API.
- Audit score, trust score, and safety policy warnings.
- Install target compatibility for Codex, Claude Code, Cursor, or CLI.
Copy prompt
Task: Use comment-mode in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20comment-mode%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/shipshitdev-comment-mode/install
Install command: npx skills add shipshitdev/skills --skill comment-mode
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Give an agent the install path, not another directory page.
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/shipshitdev-comment-mode/install
LLM text format
/api/skills/shipshitdev-comment-mode/install?format=text
Find alternatives
/api/skills/search?q=comment-mode&limit=3
Agent prompt
Use comment-mode for this task. Review https://www.openagentskill.com/api/skills/shipshitdev-comment-mode/install, then install with: npx skills add shipshitdev/skills --skill comment-modeRegistry metadata
Agent-readable profile for automatic skill selection.
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/shipshitdev-comment-mode
LLM text
/api/registry/manifest/shipshitdev-comment-mode?format=text
Install alias
/api/registry/install/shipshitdev-comment-mode
Recommend
/api/registry/recommend?task=Use%20comment-mode%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Cursor, Browser agents
Audit report
Needs review · 71/100
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Needs validation for GitHub automation
Do a manual repository review before adding this to an agent workflow.
Role in stack
Needs validation
Primary fit
GitHub automation
Trust label
Needs manual review
Install path
Command ready
Use when
- GitHub automation workflows
- Claude Code teams
- builders willing to evaluate younger projects
Evidence
- recent repository activity
- install command or GitHub repo available
- 57/100 quality profile
review first
- Low GitHub adoption signal
- Repository license detected as Unknown, though plugin.json declares MIT. This mismatch may cause compliance ambiguity.
- No OpenAgentSkill engagement data yet
Implementation path
- 1Install it in a sandbox agent and run one GitHub automation task end to end.
- 2Compare output quality, latency, and failure behavior against at least one alternative.
- 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.
Trust profile
Do not auto-install
Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.
GitHub adoption
CHECK33 GitHub stars
Stars/forks activity
CHECK33 stars, 3 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2d since push
License clarity
CHECKUnknown
Good signals
- AI review approved
- Install path is available
- Repository evidence is available
- Recently maintained repository
- Install command has no obvious high-risk pattern
- Outcome loop is ready but needs first real agent run
Review before install
- Repository license detected as Unknown, though plugin.json declares MIT. This mismatch may cause compliance ambiguity.
- Financial research output is not financial advice; require human review before any live investment decision.
- License is unclear
- Low GitHub adoption signal
- Quality score needs review
- Permission surface needs review: shell or command execution, filesystem or document access
- GitHub adoption: 33 GitHub stars
- Stars/forks activity: 33 stars, 3 forks; issue activity unavailable in current metadata
- License clarity: Unknown
- Permission surface: shell or command execution, filesystem or document access
- No real agent outcome reports yet
- Human review required before unattended installation
Recommended action
Choose a stronger alternative or inspect the source manually before any install attempt.
Quality profile
Promising candidate for agent workflows
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Use this skill in these scenarios
Manage repositories
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Collect structured data
Web scraping
I need my agent to scrape websites and extract structured data from pages.
Build and ship code
Coding agents
I need a coding agent that can understand a repository, edit code, and review pull requests.
Workflow fit
Add it to a complete workflow
Scrape, clean, and reuse web data
Web data pipeline
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Turn skills into distribution
Content growth agent
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Ingest, retrieve, and cite
RAG knowledge base
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Compare before you install
Similar skills that may fit this task.
Code Review
Review a branch or diff against repository standards and the originating spec in two independent analysis passes.
Grill With Docs
A relentless interview that pressure-tests a plan against the codebase, sharpens domain language, and updates CONTEXT.md and ADRs when decisions become durable.
To Spec
Turn the current conversation and codebase context into a structured implementation spec, then publish it to the configured project issue tracker.
To Tickets
Break a plan, spec, or conversation into independently actionable tracer-bullet tickets with explicit blocking relationships.
Overview
--- name: comment-mode description: Granular feedback on drafts without rewriting. Generates highlighted HTML with click-to-reveal inline comments. Use when user says "comment on this", "leave comments on", "give feedback on", or asks for feedback on a draft. Supports multiple lenses—editor feedback, POV simulation ("as brian would react"), or focused angles ("word choice only", "weak arguments"). A granular alternative to rewrites that lets users review feedback incrementally without losing their voice. metadata: version: "1.0.0" tags: "feedback, comments, editing" allowed-tools: Bash(open *) Write disable-model-invocation: true ---
# Comment Mode
Generate highlighted HTML with click-to-reveal comments for granular feedback on text. Alternative to rewrites—user keeps their voice, reviews feedback incrementally.
## Contract
Inputs:
- The draft text to comment on (pasted inline or as a file path) - Optional lens: editor feedback, POV simulation (e.g. "as brian would react"), or focused angle (e.g. "word choice only")
Outputs:
- An HTML file at `_private/views/{name}-comments-temp.html` with highlighted spans and click-to-reveal comment overlays
Creates/Modifies:
- Writes `_private/views/{name}-comments-temp.html`
External Side Effects:
- Runs `open _private/views/{name}-comments-temp.html` to launch the file in the default browser
Confirmation Required:
- None — the file is a temp view artifact in `_private/` and does not modify source files
Delegates To:
- None.
## When to Use
- User says: "comment on this", "leave comments on", "give feedback on" - User pastes text and asks for feedback/critique - User wants targeted feedback without a full rewrite
## Clarify Before Commenting
Use AskUserQuestion to clarify scope when the request is ambiguous. Avoid over-commenting (overwhelming) or under-commenting (missing the point).
**Clarify when:**
- No lens specified → ask what angle they want - Long document → ask if they want full coverage or just key sections - Unclear audience → ask who the recipient is (affects POV comments)
**Skip clarification when:**
- Lens is explicit ("comment on word choice only") - Document is short (<500 words) - Context is obvious from conversation
**Example clarification:**
``` User: "comment on this" [long doc, no lens specified]
→ Use AskUserQuestion: "What should I focus on?" Options: - "Editor feedback (structure, clarity, word choice)" - "Recipient POV (how [person] would react)" - "Specific angle (tell me what)" ```
## Lenses
| Lens | Color | Comment style | |------|-------|---------------| | Editor | Yellow (#fff3cd) | observations, suggestions: "weak opener", "add proof here" | | POV (as person) | Blue (#e3f2fd) | reactions from that person's perspective: "i know this already", "legal would freak out" | | Focused | Yellow | specific angle only: "word choice", "tone", "weak arguments" |
## Comment Style
- Always lowercase - Short (5-15 words) - Smart about type: observations when noting, suggestions when alternatives help, reactions when simulating POV - Only comment where there's something worth saying—sparse beats exhaustive
## Output Rules
**DO:**
- Write to `_private/views/{name}-comments-temp.html` - Open with `open _private/views/{name}-comments-temp.html` - Use highlight colors matching the lens - Keep comments sparse and high-signal
**DO NOT:**
- Comment on everything—only where there's an obvious edit or insight - Over-explain in comments—keep them punchy - Mix lenses in one output—pick one and stick to it
## Template
```html <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>{title}</title> <style> * { box-sizing: border-box; } body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif; max-width: 700px; margin: 0 auto; padding: 40px 20px; line-height: 1.7; color: #1a1a1a; background: #fafafa; } h1, h2, h3 { margin-top: 2em; font-weight: 600; } h1 { font-size: 1.4em; } h2 { font-size: 1.2em; color: #333; } p { margin: 1em 0; }
.highlight { background: {highlight-bg}; /* #fff3cd yellow for editor, #e3f2fd blue for POV */ padding: 1px 4px; border-radius: 3px; cursor: pointer; border-bottom: 2px solid {highlight-border}; /* #ffc107 for editor, #2196f3 for POV */ transition: background 0.15s; } .highlight:hover, .highlight.active { background: {highlight-hover}; /* #ffe69c for editor, #bbdefb for POV */ }
.comment { display: none; background: {comment-bg}; /* #1a1a1a for editor, #0052cc for POV */ color: #fff; padding: 8px 12px; border-radius: 6px; font-size: 0.85em; margin: 8px 0; line-height: 1.5; } .comment.show { display: block; }
.section-break { border: none; border-top: 1px solid #ddd; margin: 2em 0; }
.legend { position: fixed; bottom: 20px; right: 20px; background: #fff; padding: 12px 16px; border-radius: 8px; box-shadow: 0 2px 12px rgba(0,0,0,0.1); font-size: 0.8em; color: #666; } </style> </head> <body>
{content with <span class="highlight" data-comment="comment text">highlighted phrase</span>}
<div class="legend">{count} comments · click highlights to reveal</div>
<script> document.querySelectorAll('.highlight').forEach(el => { const commentText = el.getAttribute('data-comment'); const commentDiv = document.createElement('div'); commentDiv.className = 'comment'; commentDiv.textContent = commentText; el.insertAdjacentElement('afterend', commentDiv);
el.addEventListener('click', () => { const wasActive = el.classList.contains('active'); document.querySelectorAll('.highlight').forEach(h => h.classList.remove('active')); document.querySelectorAll('.comment').forEach(c => c.classList.remove('show')); if (!wasActive) { el.classList.add('active'); commentDiv.classList.add('show'); } }); }); </script> </body> </html> ```
### Color Reference
**Editor lens (yellow):**
```css .highlight { background: #fff3cd; border-bottom: 2px solid #ffc107; } .highlight:hover, .highlight.active { background: #ffe69c; } .comment { background: #1a1a1a; } ```
**POV lens (blue):**
```css .highlight { background: #e3f2fd; border-bottom: 2px solid #2196f3; } .highlight:hover, .highlight.active { background: #bbdefb; } .comment { background: #0052cc; } ```
## Workflow
1. User pastes text + asks for comments 2. **If ambiguous**: Use AskUserQuestion to clarify lens/scope 3. Read text, identify key phrases worth commenting on (sparse, high-signal) 4. Generate HTML with highlights and `data-comment` attributes 5. Write to `_private/views/{name}-comments-temp.html` 6. Run `open _private/views/{name}-comments-temp.html`
## Examples
**Editor lens:**
``` User: "comment on this, focus on word choice" → Yellow highlights, suggestions like "vague, try 'specifically'" or "jargon, simplify" ```
**POV lens:**
``` User: "comment on this as brian would react" → Blue highlights, reactions like "i already know this" or "legal would push back here" ```
**Focused lens:**
``` User: "leave comments on this, only flag weak arguments" → Yellow highlights on weak claims, comments like "needs evidence" or "assumes too much" ```
**Sparse/sharp lens:**
``` User: "comment only where there's an obvious fix" → Minimal highlights, only typos, missing words, or clear improvements ```
Technical details
- Version
- 1.0.0
- License
- Unknown
- Last updated
- Aug 23, 2026
- Published
- Aug 23, 2026
Decision snapshot
Needs validation
recent repository activity
Audit
Install review
Install and adoption review
- Security
- 67/100
- Maintenance
- 100/100
- Install
- 92/100
Agent-proven evidence
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
- Success rate
- —
- Recent failure
- —
- Outcomes
- 0
- Output quality
- —
- Failed
- 0
- Not relevant
- 0
- Installs
- 0
- Risk blocked
- 0
- Setup needed
- 0
- Production
- 0
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Add to agent workflow
Free and open source. Review the report before installing into production agents.
Growth loop
Share kit
Scenario-led draft for comment-mode, ready for a manual X post.
comment-mode: Granular feedback on drafts without rewriting. Generates highlighted HTML with click-to-revea... 33 stars https://www.openagentskill.com/skills/shipshitdev-comment-mode?ref=x
Optional reply with install command
Listing + install path for comment-mode: https://www.openagentskill.com/skills/shipshitdev-comment-mode?ref=x Install: npx skills add shipshitdev/skills --skill comment-mode
Listing source
Registry indexed
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
- Creator
- shipshitdev
- Source
- shipshitdev/skills
- Indexed by
- OpenAgentSkill community index
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
Claim this skill listing
This Registry indexed listing is attributed to shipshitdev but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Add the evidence badges to your README
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/shipshitdev-comment-mode)
[](https://www.openagentskill.com/skills/shipshitdev-comment-mode)
[](https://www.openagentskill.com/skills/shipshitdev-comment-mode/audit)
[](https://www.openagentskill.com/skills/shipshitdev-comment-mode)Author
shipshitdev
@shipshitdev
Tags
Platform fit
Health signals
- GitHub stars
- 33
- Quality score
- 34/100
- Last GitHub push
- Aug 20, 2026
- Framework hints
- Unknown
- OpenAgentSkill views
- 0
- Install copies
- 0
- Outbound clicks
- 0
Community signal
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Trust & safety
Do not auto-install
- GitHub adoption33 GitHub starsCHECK
- Stars/forks activity33 stars, 3 forks; issue activity unavailable in current metadataCHECK
- Recent maintenance2d since pushPASS
- License clarityUnknownCHECK
- README/SKILL.md completenessMetadata includes enough usage and workflow contextPASS
- Dependency/runtime riskcommand execution surface, network or browser surfaceINFO
Related skills
Code Review
Review a branch or diff against repository standards and the originating spec in two independent analysis passes.
168.6K StarsGrill With Docs
A relentless interview that pressure-tests a plan against the codebase, sharpens domain language, and updates CONTEXT.md and ADRs when decisions become durable.
164.7K StarsTo Spec
Turn the current conversation and codebase context into a structured implementation spec, then publish it to the configured project issue tracker.
164.7K StarsTo Tickets
Break a plan, spec, or conversation into independently actionable tracer-bullet tickets with explicit blocking relationships.
176.7K Stars