comment-rule

v1.1.0

One comment checker for every repo and every point in the harness: a change must not add comment lines on net, and must not add file:line citations or PR/issue/ticket history in comments. CLI for CI and merge gates, plus write-time feedback after each edit.

CodexClaude Code

By David KimLicense: MIT1 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes: Codex and Claude Code
Parsed components: 0 skill or MCP entries
Source updated: Sep 28, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install comment-rule for Codex and Claude Code

Installs for the current user

codex plugin marketplace add davekim917/bootstrap
codex plugin marketplace upgrade davekim917-bootstrap
codex plugin add comment-rule@davekim917-bootstrap

Paste and run these commands in a terminal with Codex. They add and refresh the davekim917-bootstrap catalog, then install this plugin.

Compatibility: the page URL and API slug “comment-rule” remain stable.

Codex: comment-rule@agent-plugin-marketplace → comment-rule@davekim917-bootstrap

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/davekim917/bootstrap

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/comment-rule/.

Plugin files

plugins/comment-rule/

├── .codex-plugin/plugin.json
└── .claude-plugin/plugin.json

Plugin manifests2

plugins/comment-rule/.codex-plugin/plugin.json

{
  "name": "comment-rule",
  "version": "1.1.0",
  "description": "One comment checker for every repo and every point in the harness: a change must not add comment lines on net, and must not add file:line citations or PR/issue/ticket history in comments. CLI for CI and merge gates, plus write-time feedback after each edit.",
  "author": {
    "name": "David Kim"
  },
  "repository": "https://github.com/davekim917/bootstrap",
  "license": "MIT",
  "keywords": [
    "comments",
    "code-quality",
    "ci",
    "typescript",
    "python",
    "sql",
    "dbt",
    "shell"
  ],
  "hooks": "./hooks/comment-rule-codex-hooks.json",
  "interface": {
    "displayName": "Comment rule",
    "shortDescription": "No net comment growth; no file:line or PR-number comments",
    "longDescription": "Counts comment lines with a real parser per language (TypeScript/JavaScript, Python, SQL and dbt, shell) and compares a change against its base. The same checker runs in CI, in merge gates and after each edit, where it tells the agent which new comment lines it added. Feedback only at write time; CI decides.",
    "developerName": "David Kim",
    "category": "Coding",
    "capabilities": [
      "Interactive"
    ],
    "websiteURL": "https://github.com/davekim917/bootstrap",
    "brandColor": "#0f766e"
  }
}

plugins/comment-rule/.claude-plugin/plugin.json

{
  "name": "comment-rule",
  "version": "1.1.0",
  "description": "One comment checker for every repo and every point in the harness: a change must not add comment lines on net, and must not add file:line citations or PR/issue/ticket history in comments. CLI for CI and merge gates, plus write-time feedback after each edit.",
  "author": {
    "name": "David Kim"
  },
  "repository": "https://github.com/davekim917/bootstrap",
  "license": "MIT",
  "keywords": [
    "comments",
    "code-quality",
    "ci",
    "typescript",
    "python",
    "sql",
    "dbt",
    "shell"
  ],
  "hooks": "./hooks/comment-rule-hooks.json"
}

Browse the “comments” tag →

jev-lint

by mizchi

Lint the things a linter cannot: names that drifted from their implementation, comments that became false, tests that do not verify what they claim. ast-grep picks the code, one sentence is the rule, a model answers it. Includes the shipped rule packs, a cookbook for writing your own, and the calibration procedure.

Claude Code1 Skill

46Updated last week

comment-slop

by Alberto Leal

Find and remove redundant comments and docstring content while retaining rationale, contracts, and documentation/tooling functions. Apply a source-based keep/delete/reduce/rewrite review; optionally consult Jev on redundancy and whether a proposed edit loses useful information. Reuses the configurable general Jev helper and skips it without helper or credentials. Use when cleaning up AI-slop comments, auditing a diff, reducing mixed docstrings, or checking a comment rewrite.

Codex1 Skill

22Updated 5 days ago

code-tidying

by Melodic Software

Code tidying and comment hygiene: /code-tidying:tidy proactively hunts a rotated, glob-scoped lane for Beck-style tidyings under a research-backed scope budget and ships one tight PR; /code-tidying:batch-simplify sweeps a time window, a branch, or an entire repository through grouped, dependency-ordered simplification waves with a fix-first deferral contract that resolves deferrals in the same run instead of filing issues; /code-tidying:dissolve-comments enforces self-describing expressive code over a diff or target, widening to the branch diff and then the whole repository when the tree is clean: it deletes zero-information comments, dissolves code-expressible ones into names and structure behind a tests gate (safe mode restricts applied edits to removals, the aggressive dial keeps only exempt surfaces and terse warnings, and strip deletes every comment but the exempt surfaces without rewriting code), and keeps only terse load-bearing comments code cannot express; /code-tidying:audit-comment-residue is a read-only classifier that flags history, plan, conversational, ticket/PR, and origin-note residue in code comments for author-applied deletion; /code-tidying:audit-dead-code is a read-only whole-repo dead-code hunter running four labeled lanes of unequal confidence (knip for TS/JS, vulture for Python, gopls for Go, and a portable grep lane for shell and PowerShell), adjudicating every candidate against dynamic-usage evidence into a dead, uncertain, or alive verdict. Project-specific tidy lanes are scaffolded into a tracked .claude/tidy-lanes/ config folder by a re-runnable setup skill.

Claude Code6 Skills

20Updated 1 hour ago

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[comment-rule on Agent Plugins Marketplace](https://pluginsmp.com/plugins/comment-rule)