generate-doc
Skill166 starsChanged 5 months agoMITView on GitHub
Use for OpenIAP documentation generation work, especially the release-note card each PR carries in packages/docs/src/pages/docs/updates/releases.tsx, written as already published with the expected native and framework versions and their future GitHub Release links, updating an existing unreleased train instead of creating a duplicate.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- hyochan/react-native-nitro-soundtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- hyochan/react-native-nitro-sound★ 961same name
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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/openiap-ssot.mdcCursor rule
- add-showcase-appSkill
- e2e-matrix-runner-appleSkill
- e2e-matrix-runner-googleSkill
- e2e-matrix-runnerSkill
- github-labelsSkill
- iapkit-e2e-martieSkill
- iapkit-e2e-petguSkill
- loop-reviewSkill
- opencollective-stewardSkill
- openiap-workflowsSkill
- rebase-mainSkill
- review-selfSkill
- ship-releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 9
Read that file first and follow it fully — required reading, release-note mode, version sources, tag formats, editing rules, multi-package …
- Very specific: line 18
Run the same validation commands (bunx prettier --check, bun run build, bun run audit:docs, bun run audit:release-state, git diff --check) …
≈ “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
Generate OpenIAP Docs (Claude Code)
The canonical instructions live in .codex/skills/generate-doc/SKILL.md.
Read that file first and follow it fully — required reading, release-note
mode, version sources, tag formats, editing rules, multi-package release
trains, and validation are all defined there and apply to any agent.
Claude Code Notes
- Where the canonical file says to use
openiap-workflows, use the.claude/skills/openiap-workflowsskill or the matching.claude/commands/*.mdslash command instead. - Run the same validation commands (
bunx prettier --check,bun run build,bun run audit:docs,bun run audit:release-state,git diff --check) before reporting the docs change as done.
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.