no-comments
Skill9 starsChanged 37 days agoMITView on GitHub
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
73 other projects use a version of this, 56 of them edited.
Adopted by
Most recently taken up by
- sammyjoyce/prime-pstackedited, first seen Nov 15, 2026
- pronvis/skillsedited, first seen Nov 15, 2026
- upamune/skillsedited, first seen Nov 15, 2026
- Amronos/skillsedited, first seen Nov 15, 2026
- remotion-dev/remotiontheir own version, first seen Nov 8, 2026
- paramcodes/skillsedited, first seen Nov 8, 2026
Other versions73 projects use a version of this.
Word for word · 0
None found.
Edited · 56
- backnotprop/pstack★ 3.8k62% same
- moeru-ai/xsai★ 66762% same
- jtaroreh/agystack★ 12881% same
- uzairansaruzi/p3-stack★ 12671% same
- dsebban/skills★ 7178% same
- overextended/skills★ 2241% same
- creedants/pstack-t3★ 1849% same
- painhardcore/pstack★ 1869% same
- Scino/fstack★ 1872% same
- mariusflorescu/pstack-t3★ 1361% same
46 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 repository64 other files it gives its agents.
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- blast-radiusSkill
- broSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- deslopSkill
- documentation-impactSkill
- figure-it-outSkill
- howSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- poteto-helpSkill
- poteto-modeSkill
- poteto-tddSkill
- poteto-teachSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- 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
- pr-recapSkill
- pstack-harnessSkill
- recallSkill
- reflectSkill
- runtime-probesSkill
- setup-pstackSkill
- sharpenSkill
- show-me-your-workSkill
- spec-probesSkill
- statechartSkill
- swarmSkill
- technical-writingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 1 is common, 0 are distinctive, and 1 is very specific to this project.
1
Common
Most of the 71 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 14
Use the caller's files or diff.
- Very specific: line 16
If the scope is a diff that adds or changes no comments, report that and stop without spawning Comment Sicko.
“Common” is measured: kept by at least 6 in 10 of the 71 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.
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.
If the scope is a diff that adds or changes no comments, report that and stop without spawning Comment Sicko. Doc comments, docstrings, and lint or type suppressions such as eslint-disable, @ts-ignore, and # noqa count as comments. When unsure, spawn it.
Steps
- Resolve the logical persona
comment-sickothrough 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. Call the Skill tool withpstack-harnessfor the spawn. Its Spawn a role section resolves the role and builds this CLI's spawn call. - 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, call the Skill tool withhoworwhyon 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. - Fix trivial accepted flags directly by deleting a dead path, dropping a parameter, or using the real API. If any fix needs a shape, call the Skill tool with
architectonce on 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. Neither authorizes widening the fence nor fixing instances outside it. Never bolt on symptom guards.
- 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.

