no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- License 许可
- MIT
- 最近更新
- 2026-10-03
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- no-comments
- description
- Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- disable-model-invocation
- true
03 SKILL.md 正文
No comments
Spawn Comment Sicko. Act on accepted findings.
Authoring agents defend comments. Defer to Comment Sicko's fresh perspective.
Scope
Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.
Steps
- Use Comment Sicko if available. Otherwise use an available reviewer with a read-only brief to identify redundant comments and explain each proposed removal. Preserve non-obvious rationale, legal notices, and unverified constraints. If delegation is unavailable, review locally and say so.
- Inspect its report and diff. Reject application-code edits, scope escapes, exception-protected deletions, misstated
MUST KILLreasons, and flags that treat kept intentional code as guilty. Reshape flags on our-code surprises stay actionable. Do not restore those comments. A keep survives only with proof it is about something we cannot change. Audit missed scoped lint and TypeScript suppressions. Correctness or safety suppressions stay actionableMUST KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thinIMPORTANTordo not removekills or keeps, run/howor/whyon their symbol. If a removal is ambiguous, preserve the comment and report the unresolved question. Revert and rerun one rejected report with the failure named. Reject a second, report it open, and fail/no-comments. - Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, run
/architectonce for the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements. - Implement the smallest root-cause fix in scope. Remove every named workaround. If the root cause is out of scope, land the smallest in-scope fix and report the rest open. The principle-fix-root-causes and principle-redesign-from-first-principles skills guide intent only: fix real causes, redesign as if requirements always existed, never bolt on symptom guards. Neither authorizes widening the fence nor fixing instances outside it.
- Constraint comments say
do not remove,do not change wording, ortalk to X before changing. Leave keeps about things we cannot change. Encode a verified constraint with the cheapest appropriate in-scope mechanism when implementation is authorized. Remove its comment only when the replacement preserves the information. If the constraint or authority is unresolved, keep the comment and report it. Do not expand a comment review into an unrelated redesign. - Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
04 同仓库更多 Skills
finance-updates
Review Koru spending, bank exports, dated holdings and monthly purchase emails, then prepare proposals for the user's review. Use with a Koru review bundle or connected Koru MCP tools.
convex
Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.
convex-setup-auth
Sets up Convex auth, identity mapping, and access control. Use for login, auth providers, users tables, protected functions, or roles in a Convex app.
convex-quickstart
Creates or adds Convex to an app. Use for new Convex projects, npm create convex@latest, frontend setup, env vars, or the first npx convex dev run.
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-migration-helper
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.