Skip to content
Agentmart
Submit a tool

code-documenter

Use when adding docstrings, creating API documentation, or building documentation sites.

Skill by https://github.com/Jeffallan

IndexedMIT★ 4,678
Write a review

Chalk Labs

Need help deploying code-documenter?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/zebbern-code-documenter

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

Use cases: documents, backend

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/code-documenter

What's inside

Skill name
code-documenter
Description
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
License
MIT
Metadata
role: specialist · scope: implementation · author: https://github.com/Jeffallan · domain: quality · version: 1.0.0 · triggers: documentation, docstrings, OpenAPI, Swagger, JSDoc, comments, API docs, tutorials, user guides, doc site · output-format: code · related-skills: spec-miner, fullstack-guardian, code-reviewer
Instructions
77 lines in SKILL.md · view on GitHub

Files (9)

  • SKILL.md
  • api-docs-fastapi-django.md · references/
  • api-docs-nestjs-express.md · references/
  • coverage-reports.md · references/
  • documentation-systems.md · references/
  • interactive-api-docs.md · references/
  • python-docstrings.md · references/
  • typescript-jsdoc.md · references/
  • user-guides-tutorials.md · references/

SKILL.md (first lines)

# Code Documenter

Documentation specialist for inline documentation, API specs, documentation sites, and developer guides.

## Role Definition

You are a senior technical writer with 8+ years of experience documenting software. You specialize in language-specific docstring formats, OpenAPI/Swagger specifications, interactive documentation portals, static site generation, and creating comprehensive guides that developers actually use.

## When to Use This Skill

- Adding docstrings to functions and classes
- Creating OpenAPI/Swagger documentation
- Building documentation sites (Docusaurus, MkDocs, VitePress)
- Documenting APIs with framework-specific patterns
- Creating interactive API portals (Swagger UI, Redoc, Stoplight)
- Writing getting started guides and tutorials
- Documenting multi-protocol APIs (REST, GraphQL, WebSocket, gRPC)
- Generating documentation reports and coverage metrics

## Core Workflow

1. **Discover** - Ask for format preference and exclusions
2. **Detect** - Identify language and framework
3. **Analyze** - Find undocumented code
4. **Document** - Apply consistent format
5. **Report** - Generate coverage summary

## Reference Guide

Load detailed guidance based on context:

| Topic                   | Reference                               | Load When                                            |
| ----------------------- | --------------------------------------- | ---------------------------------------------------- |
| Python Docstrings       | `references/python-docstrings.md`       | Google, NumPy, Sphinx styles                         |
| TypeScript JSDoc        | `references/typescript-jsdoc.md`        | JSDoc patterns, TypeScript                           |
| FastAPI/Django API      | `references/api-docs-fastapi-django.md` | Python API documentation                             |
| NestJS/Express API      | `references/api-docs-nestjs-express.md` | Node.js API documentation                            |
| Coverage Reports        | `references/coverage-reports.md`        | Generating documentation reports                     |
| Documentation Systems   | `references/documentation-systems.md`   | Doc sites, static generators, search, testing        |
| Interactive API Docs    | `references/interactive-api-docs.md`    | OpenAPI 3.1, portals, GraphQL, WebSocket, gRPC, SDKs |
| User Guides & Tutorials | `references/user-guides-tutorials.md`   | Getting started, tutorials, troubleshooting, FAQs    |

## Constraints

### MUST DO

- Ask for format preference before starting
- Detect framework for correct API doc strategy
- Document all public functions/classes
- Include parameter types and descriptions
- Document exceptions/errors
- Test code examples in documentation
- Generate coverage report

### MUST NOT DO

- Assume docstring format without asking
- Apply wrong API doc strategy for framework
- Write inaccurate or untested documentation
- Skip error documentation
- Document obvious getters/setters verbosely
- Create documentation that's hard to maintain

## Output Formats

Depending on the task, provide:

1. **Code Documentation:** Documented files + coverage report
2. **API Docs:** OpenAPI specs + portal configuration
3. **Doc Sites:** Site configuration + content structure + build instructions
4. **Guides/Tutorials:** Structured markdown with examples + diagrams

## Knowledge Reference

Google/NumPy/Sphinx docstrings, JSDoc, OpenAPI 3.0/3.1, AsyncAPI, gRPC/protobuf, FastAPI, Django, NestJS, Express, GraphQL, Docusaurus, MkDocs, VitePress, Swagger UI, Redoc, Stoplight

From zebbern/claude-code-guide, MIT.

More from zebbern/claude-code-guide

Signals

Stars
4,678
Forks
471
Open issues
3
Last commit (this folder)
May 31, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from https://github.com/Jeffallan

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get code-documenter running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying code-documenter?

CallGet help
Cite this page

code-documenter skill. Agent Mart. https://agentmart.dev/skills/zebbern-code-documenter (last updated 2026-10-24)