accelint-readme-writer

Generate and update README.md files from codebase API analysis.

21|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-readme-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-readme-writer
Source: https://github.com/gohypergiant/agent-skills/tree/main/skills/accelint-readme-writer
Command: npx skills add https://github.com/gohypergiant/agent-skills --skill accelint-readme-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

## What problem does it solve? README documentation often drifts out of sync with code. This skill analyzes the codebase from the README location and generates or updates a thorough, human-friendly README that reflects current functionality.

## Core Features & Use Cases

  • Codebase-driven API mapping: Extracts public exports, types, and usage patterns to ensure the API section matches the actual code.
  • Template-driven structure: Produces consistent READMEs with the prescribed sections (Heading Area, Installation, Quick Start, What, Why, API, Examples, License).
  • Monorepo friendly: Scopes analysis to the package containing the README, enabling precise, package-level documentation.

### Quick Start Prompt the AI with "Document this package" or "Write a README for this package" to generate a complete README aligned with the codebase.

Frequently Asked Questions about accelint-readme-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a README from my codebase?

Generate a README by prompting the AI to document the package, which analyzes the surrounding codebase, extracts public API details, and applies a standardized structure template to produce accurate documentation.

Why does my README documentation drift out of sync with code?

README documentation drifts out of sync because manual updates lag behind code changes; this skill analyzes the current codebase from the README location to generate or update human-friendly documentation reflecting actual functionality.

Can I write package-level documentation for a monorepo?

Write package-level documentation for a monorepo by scoping the codebase analysis to the specific package containing the README, enabling precise, package-level documentation instead of broad repository overviews.

What sections should a standardized README include?

A standardized README should include Heading Area, Installation, Quick Start, What, Why, API, Examples, and License sections, produced consistently through a template-driven structure aligned with the codebase.

Does the generated README extract public exports and types automatically?

The generated README extracts public exports, types, and usage patterns automatically through codebase-driven API mapping, ensuring the API section matches the actual code without manual entry.

What is the best way to update an existing README to match current code?

Update an existing README to match current code by analyzing the surrounding codebase from the README location, extracting current public API details, and refining the documentation to reflect present functionality accurately.