AST-based comments
gen-comments reads JavaScript and TypeScript syntax trees, then writes stable JSDoc blocks for named declarations.
Beautiful docs & blog,
shipped every day.
Generate JSDoc from the AST, validate it in CI, and publish a static documentation site without AI, network calls, or runtime surprises.
2 CLIs
0 AI calls
234 tests
Everything your docs need
Static docs site
gen-docs builds a searchable multi-page HTML reference from documented source files.
CI-ready checks
Use check, drift, lint, and fix modes as plain exit-code based gates in GitHub Actions.
ESLint integration
The companion ESLint plugin exposes jsdoc-scribe lint rules inside existing flat-config projects.
From the blog
View all posts →
AI
Your PR Review Queue Is Up 441%. Here''s the One Slice Generated Docs Can Actually Shrink.
LinearB's 2026 benchmarks put a number on the AI-code review slowdown — agentic PRs wait 5.3x longer for reviewer pickup. Faros's data shows why. A worked example of exactly which part of that time generated documentation removes, and which part it explicitly doesn't.
SECURITY
What the axios Compromise Should Change About How You Pick a Documentation Tool
On March 31, 2026, axios — one of the most-downloaded packages on npm — was compromised via maintainer credential theft. That incident, and the 1.2M+ malicious packages now blocked cumulatively across the registry, make a devDependency's own dependency tree a real audit question, not a nitpick. Here's how to actually check one, using jsdoc-scribe's package.json as the worked example.
DUEDILIGENCE
The Due-Diligence Question That Doesn''t Ask Who Wrote Your Code
Two independently-run 2026 due-diligence checklists just added the same new category — not who wrote a system, but whether anyone can explain it. Here's what actually answers that question, and why a clean demo stopped being enough.