no-comments
Review Roblox Luau comments and suppressions, deleting narration while preserving non-obvious invariants, platform constraints, and authored contracts.
- License 许可
- MIT
- 最近更新
- 2026-09-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- no-comments
- description
- Review Roblox Luau comments and suppressions, deleting narration while preserving non-obvious invariants, platform constraints, and authored contracts.
02 资源文件 2
- 参考文档agents/openai.yaml203 B
- 参考文档references/comment-sicko-prompt.md2.3 KB
03 SKILL.md 正文
Comment review
Review only the requested files or current diff.
- Classify each comment as narration, stale explanation, workaround, invariant, platform constraint, security boundary, data migration note, authored-asset contract, or public API documentation.
- Delete narration that repeats the code. Improve names, types, data shapes, or module boundaries when a comment exists only because the code is hard to follow.
- Keep a concise comment when it explains a non-obvious reason the code cannot express, including Roblox engine behavior, ordering, replication, persistence, security, or authoring constraints.
- Verify claims against source, repository guidance, and current Roblox behavior when the claim may have changed. Use
$howor$whyfor uncertain constraints. - Treat analyzer suppressions and casts as evidence. Remove them only after the root cause is fixed and the relevant check passes.
- Report deleted, rewritten, and retained comments with the reason for every retained exception.
Never trade a useful invariant for silence. The target is less reader work, not zero comments.
04 同仓库更多 Skills
why
Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.
unslop
Cut AI tells from any writing. Must always apply.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.
swarm
Coordinate independent routine execution or exploration batches and return one reviewed report. Use for $swarm or large separable work that justifies parallel overhead.