editing-files
Skill2 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Edits text files of any kind. What this does is defining a set of rules to follow when editing or creating any file. Use this when the user is asking to create or edit any file or when you need to create or edit files.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- addressing-pull-request-commentsSkill
- analyzing-github-issueSkill
- applying-ruby-conventionsSkill
- applying-test-conventionsSkill
- committing-changesSkill
- creating-pull-requestSkill
- enforcing-project-rulesSkill
- implementing-github-issueSkill
- improving-agent-reflectionSkill
- running-cli-in-wsl-portableSkill
- syncing-branch-with-baseSkill
- updating-docSkill
- validating-production-qualitySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 10
Always tell the user "SKILL: I am editing files" to inform the user that you are running this skill.
- Distinctive: line 14
Always end any text file with an empty line.
≈ “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
Editing files
Inform the user
- Always tell the user "SKILL: I am editing files" to inform the user that you are running this skill.
Rules to be followed when editing files
- Always end any text file with an empty line.
For example, avoid this:
puts 'Hello World'``` Prefer this: ```ruby puts 'Hello World' - When editing big files,
agent: replace_in_filetool may not work properly. Always check that the file is containing the edits you expect. If the edits were not performed, then always useagent: write_in_filewith the whole file's content.
When to use it
- Always use it every time another skill specifically mentions
skill: editing-files. - Always use it every time the user asks you to create or edit a file.
- Always use it every time you need to create or edit a file.
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.

