py-clean-functions
Skill2 starsChanged 3 months agoLicence not identifiedView on GitHub
Use when writing, fixing, editing, or refactoring Python functions. Enforces Clean Code principles—maximum 3 arguments, single responsibility, no flag parameters. Also trigger on: functions with 4+ parameters, boolean flag parameters like `enabled=True`, functions that mutate their arguments in place, one-off `util`/`helper` functions that are never called, or asks like "too many arguments", "split this function", "is this still used". Also trigger on: helper functions defined above the entry point that calls them, a module that has to be read bottom-up, a function mixing orchestration with low-level detail, or asks like "does this read top-down", "stepdown rule", "should this read like a book", "what order should these functions go in".
In this repository27 other files it gives its agents.
- design-patternsSkill
- go-api-designSkill
- go-concurrencySkill
- go-errorsSkill
- go-idiomSkill
- go-interfacesSkill
- go-testsSkill
- java-boy-scoutSkill
- java-clean-codeSkill
- java-clean-commentsSkill
- java-clean-functionsSkill
- java-clean-generalSkill
- java-clean-namesSkill
- java-clean-testsSkill
- py-boy-scoutSkill
- py-clean-commentsSkill
- py-clean-generalSkill
- py-clean-namesSkill
- py-clean-testsSkill
- python-clean-codeSkill
- ts-boy-scoutSkill
- ts-clean-commentsSkill
- ts-clean-functionsSkill
- ts-clean-generalSkill
- ts-clean-namesSkill
- ts-clean-testsSkill
- typescript-clean-codeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

