Clean Up Docs Push
Skill50 starsChanged 4 months agoMITView on GitHub
Code cleanup, docs update, and git push workflow
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- alexeyleshchenko/fast-mcp-telegramword for word, first seen Jul 28, 2026
Other versions1 project uses a version of this.
Word for word · 1
- alexeyleshchenko/fast-mcp-telegram★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/code-optimization.mdcCursor rule
- .cursor/rules/docs-plain-language.mdcCursor rule
- .cursor/rules/general.mdcCursor rule
- .cursor/rules/implementation-workflow.mdcCursor rule
- .cursor/rules/memory-bank.mdcCursor rule
- feature-developmentSkill
- Release Notes GenerationSkill
- Remove Old LogsSkill
- sourcery-pr-cycleSkill
- telegram-patternsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Run linter checks on modified files
- Distinctive: line 12
Run test suite to verify everything passes
- Distinctive: line 15
Update README.md - add new features to Features table and update tool descriptions
- Very specific: line 16
Update docs/ folder - check all relevant files and update with new features
≈ “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.
Files
Workflow
- Code Cleanup (use
code-cleanup-specialistsubagent):- Run linter checks on modified files
- Fix any code quality issues
- Run test suite to verify everything passes
- Update Docs:
- Update
README.md- add new features to Features table and update tool descriptions - Update
docs/folder - check all relevant files and update with new features
- Update
- Git Push:
- Create descriptive commit
- Push to remote
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.