Open-source hub for documentation & technical-writing skills across AI coding tools (Claude Code, Cursor, Codex). 6 skills — style, terminology, link checks, coverage, changelogs — with a vendor-neutral core and optional EkLine power-ups.
Claude Code instructions for ekline-io/ekline-docs-skills, covering ekline docs skills — project guide, what this is, north star (ethos), golden rules (read before changing things) and repo map.
Generate a structured changelog entry from git history. Runs a helper script that analyzes commits and categorizes them (Added, Changed, Fixed, Removed, Security, Breaking Changes). Presents results in Keep a Changelog format. Use before a release or to catch up on missing entries.
Scan documentation files for broken internal links, missing anchors, and optionally validate external URLs. Runs a helper script that extracts all links, validates them, and reports broken links with suggestions. Use before publishing docs or as a periodic health check.
Measure documentation coverage by scanning your codebase for exported functions, classes, API endpoints, and CLI commands, then checking if docs exist. Runs a helper script that reports coverage percentage, breakdowns by type and directory, and lists undocumented items. Supports TypeScript/JavaScript, Python, and Go.
Run EkLine Docs Reviewer on documentation files and apply the recommended fixes. Use this skill when reviewing technical documentation for style and best practices, or after creating or writing technical documentation.
Enforces documentation style, voice, and tone consistency. Validates against style rules and existing documentation patterns. Run this skill proactively whenever documentation files (.md, .mdx, .rst, .adoc, .txt, .html) are created or modified.
Ensures consistent language and terminology across all documentation. Checks terms against terminology rules and flags inconsistencies. Run this skill proactively whenever documentation files (.md, .mdx, .rst, .adoc, .txt, .html) are created or modified.