Skip to main content

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

来源信息

仓库
Aqua-123/pstack-for-codex
最近来源活动
2026年10月14日 14:21
检测到的 SKILL.md 语言
英语
星标
92
Forks
16

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
3 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
no-comments
description
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
# No comments Delegation and optional capabilities follow `../poteto-mode/references/codex-agent-runtime.md`. 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 1. Spawn the namespaced Comment Sicko profile when installed. Otherwise use a generic agent seeded with `references/comment-sicko-prompt.md`. Pass the scope and require read-only analysis. If no independent agent is available, report the review capability as blocked rather than self-certifying. 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 KILL`s. Restore deletions only with exact exceptions and scoped proof. Before accepting thin `IMPORTANT` or `do not remove` kills or keeps, run `$how` or `$why` 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 fail `$no-comments`. 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, run `$architect` once for 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: fix real causes, redesign as if requirements always existed, never bolt on symptom guards. Neither authorizes widening the fence nor fixing instances outside it. 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.
在 GitHub 查看