360 Secure SkillHub
360 安全技能中心

no-comments

通过 spawn Comment Sicko 角色审查文件或 diff 中的注释,剔除无效或误报项,修复可接受的代码问题;对保留的约束注释提供类型、运行时、测试或 CI lint 编码方案,并在交互批准后执行。

mdsmithaustin
热度 0.00
最近更新 2026-10-19 07:37:02
分类:开发依赖:内部调用大模型 / 读写文件应用场景:代码审查 / 代码生成

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add mdsmithaustin/pstack/no-comments
Metadata
name
no-comments
description
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

No comments

Spawn Comment Sicko. Act on accepted findings.

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

  1. Resolve the logical persona comment-sicko through the persona contract and spawn it with the scope. Use the native persona when the live agent catalog lists it, or pass its complete bundled briefing through the selected mechanism. Preserve its rules verbatim. Use the pstack-harness skill for the spawn. Its Spawn a role section resolves the role and builds this CLI's spawn call.
  2. Inspect its report and diff. Reject application-code edits, scope escapes, exception-protected deletions, misstated MUST KILL reasons, 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 actionable MUST KILLs. Restore deletions only with exact exceptions and scoped proof. Before accepting thin IMPORTANT or do not remove kills or keeps, use the how skill or the why skill on their symbol. If a kill is ambiguous, do not restore. If a keep is refuted or still ambiguous, delete it. Revert and rerun one rejected report with the failure named. Reject a second, report it open, and end this skill's run as failed.
  3. Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, use the architect skill once on the accepted set and surrounding code. Stop at the sketch. Architect shapes. Step 4 implements.
  4. 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. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
  5. Constraint comments say do not remove, do not change wording, or talk to X before changing. Leave keeps about things we cannot change. Offer the cheapest in-scope type, runtime, test, or CI lint. Wait for interactive approval. Unattended and eval require caller pre-approval. If approved, encode then delete. Otherwise delete, report the constraint open, and sketch out-of-scope work.
  6. Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.