Individual skill
document-code
AI DevKit · Document a code entry point with structured analysis, dependency mapping, and saved knowledge docs. Use when users ask to document, understand, or map code for a module, file, folder, function, or API.
skills/document-code/SKILL.md
Source commit d2e170abef698edb63c3a39ba8fce569b6fe4b2c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,657
- Repository last updated
- Nov 4, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude-code Repository topic
- antigravity Repository topic
- agent-skills Repository topic
- agent-framework Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- cli Repository topic
- codex-cli Repository topic
- coding-agents Repository topic
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,140 bytesSKILL.mdcore · 4,140 bytesagents/openai.yamlasset · 321 bytes
Read excerpt
# Code Documentation Assistant
Build structured understanding of code entry points with an analysis-first workflow.
## Hard Rule
- Do not create documentation until the entry point is validated and analysis is complete.
## Workflow
1. Gather & Validate
- Confirm entry point (file, folder, function, API), purpose, and desired depth.
- Verify it exists; resolve ambiguity or suggest alternatives if not found.
- Search for existing knowledge before analyzing: `npx ai-devkit@latest memory search --query "<entry point name or purpose>"`