no-comments
Skill18 starsChanged 53 days agoMITView on GitHub
Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
68 other projects use a version of this, 51 of them edited.
Adopted by
Most recently taken up by
- remotion-dev/remotiontheir own version, first seen Nov 8, 2026
- paramcodes/skillsedited, first seen Nov 8, 2026
- endqwerty/endstackedited, first seen Nov 8, 2026
- tristanphvn/keeledited, first seen Nov 8, 2026
- therealmarzouq/skillstheir own version, first seen Nov 8, 2026
- hidenobunagai/astackedited, first seen Nov 8, 2026
Used with
Projects with it also use poteto-help, setup-pstack and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 13 projects that use this
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 22 projects that use this
ianclearySkillprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 25 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 16 projects that use this
TheOnlyFusionCubeSkillmaintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.
Also in 19 projects that use this
TheOnlyFusionCubeSkillcreate-formal-verification-skill
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, \"model-check this race\", \"prove this invariant\", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
Also in 21 projects that use this
- +1 more from TheOnlyFusionCube
Other versions68 projects use a version of this.
Word for word · 0
None found.
Edited · 51
- backnotprop/pstack★ 3.8k61% same
- moeru-ai/xsai★ 66761% same
- jtaroreh/agystack★ 12893% same
- uzairansaruzi/p3-stack★ 12671% same
- dsebban/skills★ 7176% same
- overextended/skills★ 2240% same
- creedants/pstack-t3★ 1848% same
- painhardcore/pstack★ 1869% same
- mariusflorescu/pstack-t3★ 1362% same
- adjohn/pstack★ 984% same
41 more not listed
Wrote their own version · 17
- remotion-dev/remotion★ 72ksame name
- Dimon94/dverity★ 107same name
- Dimon94/skills★ 107same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- cutfac/cutfac★ 14same name
- educlopez/mallard★ 4same name
- requie/endostack★ 4same name
- stainless-code/lossless★ 4same name
- fullerzz/agent-skills★ 2same name
- niksavis/basicly★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architectSkill
- arenaSkill
- automate-meSkill
- babysitSkill
- blast-radiusSkill
- broSkill
- browseSkill
- ceo-reviewSkill
- changelog-to-postSkill
- create-verification-skillSkill
- customer-lensSkill
- deslopSkill
- engineer-modeSkill
- figure-it-outSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- founder-modeSkill
- founder-voiceSkill
- fstackSkill
- geo-pageSkill
- get-pr-commentsSkill
- howSkill
- inbox-triageSkill
- interrogateSkill
- lead-replySkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- office-hoursSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-clear-namingSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- recallSkill
- reflectSkill
- retroSkill
- setup-fstackSkill
- show-me-your-workSkill
- social-postSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 66 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 17
Use the caller's files or diff.
“Common” is measured: kept by at least 6 in 10 of the 66 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
No comments
Spawn comment-sicko. Act on accepted findings.
Authoring agents defend comments. Defer to comment-sicko's fresh perspective.
Platform note. On Codex, the comment-sicko subagent and the Claude tool names below are Claude defaults. Resolve them via codex-tools.md.
Scope
Use the caller's files or diff. Otherwise use the current diff against the base branch, default main, including the working tree.
Steps
- Spawn an
Agentwithsubagent_type: "comment-sicko". Pass the scope. Do not restate its rules. - 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 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. - 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. 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. - Report the deletion count, restored comments, reruns, architect sketch, fixes, encoding offers, encodings, unenforced constraints, and other open work.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

