technical-writing-revision
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Revises technical docs and UI copy using a self-editing checklist (sentence structure, voice, verbs, terminology, paragraphs, headings, tone, errors, i18n) with Good/Bad patterns. Use when drafting or polishing READMEs, API docs, handbooks, error messages, release notes, or when the user asks for technical writing review, 推敲, テクニカルライティング, or editing English/Japanese developer-facing text.
In this repository7 other files it gives its agents.
- agent-logSkill
- deep-understandingSkill
- git-commit-messageSkill
- git-pr-draftSkill
- git-pr-reviewSkill
- grill-meSkill
- japanese-tech-writingSkill
The 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.