Design First
techygarg/lattice
Guide structured design thinking through 5 progressive levels before any code is written.
Agent skill
Developer Docs Editing Review
by hashgraph-online in hashgraph-online/awesome-codex-plugins
Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback…
Install Developer Docs Editing Review
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .claude/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .claude/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .agents/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .agents/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .cursor/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .cursor/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/LVTD-LLC/skills/skills/developer-docs-editing-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .gemini/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .gemini/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .github/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .github/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins developer-docs-editing-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review .opencode/skills/developer-docs-editing-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "developer-docs-editing-review" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/LVTD-LLC/skills/skills/developer-docs-editing-review into .opencode/skills/developer-docs-editing-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "developer-docs-editing-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
developer-docs-editing-review- GitHub stars
- 1.2k
- Token cost
- ~853 tokens
- SKILL.md length
- 340 words
- Files
- 5 (incl. references)
- Skills in repo
- 686
- Repo updated
- First seen
- Licence
- MIT
At a glance
Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback…
- Works in 6 steps: Load guidelines.md to choose the… → Identify doc type, audience, source of… → Use separate passes for technical… → …
- Preparing developer docs for release
- SKILL.md covers Quick Start, Default Output, Contents and Core Posture
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Developer Docs Editing Review is an agent skill from hashgraph-online/awesome-codex-plugins. Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `guidelines.md`, `references/core/knowledge.md` and `workflows/edit-developer-doc.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.
It sits in Development, covering Performance reviews and Refactoring. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.
When your agent uses it
- Preparing developer docs for release
- Especially docs with procedures
- High-risk technical claims
Example prompts
- “/developer-docs-editing-review”
Requirements
- Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Load guidelines.md to choose the smallest useful reference set.
- Identify doc type, audience, source of truth, and release risk.
- Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.
- Use workflows/verify-technical-doc.md when procedures, migrations, security, data, or production changes need formal verification.
- Use workflows/edit-developer-doc.md for a full edit.
- Return findings first when the user asks for a review; return revised text when the user asks for an edit.
What it can do on your machine
Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
link.springer.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
From compatibility in the SKILL.md frontmatter.
Context cost
Developer Docs Editing Review loads about 853 tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 103 tokens; SKILL.md has 340 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its MIT licence (© hashgraph-online). 340 words, ~853 tokens.
Download SKILL.mdSave it as
.claude/skills/developer-docs-editing-review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- developer-docs-editing-review
- description
- Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
- license
- MIT
- metadata.version
- 0.1.0
- metadata.displayName
- Developer Docs Editing Review
- metadata.category
- Writing
- metadata.tags
- developer-docs,technical-writing,documentation,editing,review
Developer Docs Editing Review
Use this skill to improve developer documentation after a draft exists. It treats editing as validation and refactoring: check whether the doc is accurate, complete, structured, clear, brief, and reviewable.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 4, "Editing documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 15, "Technical Editing," and Chapter 16, "Technical Verification." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.mdto choose the smallest useful reference set. - Identify doc type, audience, source of truth, and release risk.
- Use separate passes for technical accuracy, completeness, structure, clarity, and brevity.
- Use
workflows/verify-technical-doc.mdwhen procedures, migrations, security, data, or production changes need formal verification. - Use
workflows/edit-developer-doc.mdfor a full edit. - Return findings first when the user asks for a review; return revised text when the user asks for an edit.
Default Output
When reviewing documentation, return:
- Findings - ordered by reader risk, with file/section references when available.
- Missing validation - commands, examples, screenshots, API facts, or source claims not checked.
- Verification route - self-test, SME review, QA test, or release blocker.
- Recommended edits - exact changes or rewrites.
- Review routing - who should validate technical details.
- Residual risk - assumptions that remain after the edit.
When editing directly, return the revised doc plus a brief change summary and unresolved questions.
Contents
| Need | Start Here |
|---|---|
| Understand editing passes | references/core/knowledge.md |
| Apply review rules | references/core/knowledge.md |
| See examples of edits and feedback | references/core/knowledge.md |
| Run a full edit | workflows/edit-developer-doc.md |
| Verify risky technical docs | workflows/verify-technical-doc.md |
| Route by task | guidelines.md |
Core Posture
- Separate writing from editing; do not polish around an unverified flaw.
- Prioritize reader-impacting errors over style preferences.
- Ask for specific reviews from the right technical owners.
- Treat high-risk procedures as release-blocking until verified or explicitly accepted.
- Integrate feedback by user need, not by reviewer rank or comment volume.
© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in plugins/LVTD-LLC/skills/skills/developer-docs-editing-review of hashgraph-online/awesome-codex-plugins.
- SKILL.md
- guidelines.md
- references/core/knowledge.md
- workflows/edit-developer-doc.md
- workflows/verify-technical-doc.md
Open the folder on GitHubat commit 78497e5
Compare with similar skills
Developer Docs Editing Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Developer Docs Editing Review this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~853 | Automated safety check: Pass | MIT | |
| Design Firsttechygarg/lattice | 198 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Guidelinesakash-network/node | 1.1k | 22 repos | ~577 | Automated safety check: Pass | MIT | |
| Component Refactoringlangflow-ai/langflow | 156k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
Component Refactoring
langflow-ai/langflow
Refactor high-complexity React components in Langflow frontend.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Codex
skills-directory/skill-codex
A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
More from hashgraph-online/awesome-codex-plugins
All 686 skills in this repoAnime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Manuscript Engagement Analytics
hashgraph-online/awesome-codex-plugins
Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…
Related
Categories
Questions about Developer Docs Editing Review
What does Developer Docs Editing Review do?
Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback…. Developer Docs Editing Review is an agent skill from hashgraph-online/awesome-codex-plugins. Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration.
When should I use Developer Docs Editing Review?
Developer Docs Editing Review fits situations like: preparing developer docs for release; especially docs with procedures; high-risk technical claims.
How do I install Developer Docs Editing Review in Claude Code?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-editing-review in hashgraph-online/awesome-codex-plugins) into .claude/skills/developer-docs-editing-review in your project. Claude Code loads it when a task matches its description.
How do I install Developer Docs Editing Review in Codex?
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/developer-docs-editing-review in hashgraph-online/awesome-codex-plugins) into .agents/skills/developer-docs-editing-review in your project. Codex loads it when a task matches its description.
Can I use Developer Docs Editing Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill developer-docs-editing-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developer-docs-editing-review, .gemini/skills/developer-docs-editing-review, .github/skills/developer-docs-editing-review and .opencode/skills/developer-docs-editing-review in your project.
What does Developer Docs Editing Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Developer Docs Editing Review is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..
Does Developer Docs Editing Review access the network?
SKILL.md names 1 domain. As links in the text: link.springer.com. This is read from the text; nothing was executed.
Is Developer Docs Editing Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Developer Docs Editing Review use?
Developer Docs Editing Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Developer Docs Editing Review use?
About 853 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Developer Docs Editing Review?
Skills that share tags, products or a category with Developer Docs Editing Review: Design First (techygarg/lattice, 198 stars), Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars) and Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Developer Docs Editing Review?
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.