Can I review specific files instead of the whole project?

Yes, you can pass specific file paths as arguments to the skill to limit the scope of the review to just those documents.

Is an API token required to use this skill?

Yes, you must set the EKLINE_EK_TOKEN or EK_TOKEN environment variable using a token from the EkLine dashboard.

Does this skill automatically change my files?

No, it presents findings first and asks for your permission to apply all fixes, review them individually, or apply them by specific category.

What categories of issues does it detect?

It identifies issues related to grammar, terminology, style, and document structure based on professional technical writing standards.

What file types does the Review Docs skill support?

It primarily targets technical documentation files like Markdown and other text-based formats supported by the EkLine Docs Reviewer CLI.

EkLine Documentation Reviewer

Name: EkLine Documentation Reviewer
Author: ekline-io

byekline-io

•

Learning & Documentation

Analyzes technical documentation for style, grammar, and best practices and automatically applies suggested improvements.

The Review Docs skill integrates the EkLine Docs Reviewer into your Claude Code workflow, allowing for automated auditing of technical documentation. It scans directories or specific files to identify issues across categories like grammar, terminology, style, and document structure. Once issues are identified, the skill enables an interactive remediation process where users can review findings and use Claude to apply AI-driven fixes directly to the source files, ensuring your project documentation remains professional, consistent, and error-free.

Key Features

01Interactive fix application via individual review or batch updates

022 GitHub stars

03Detection of terminology and structural inconsistencies

04Automated documentation auditing for style and grammar

05Support for directory-wide or file-specific reviews

06Seamless integration with Claude's Edit tool for direct file modification

Use Cases

01Ensuring consistency in style and terminology across a large documentation site

02Automatically correcting grammar and formatting errors in Markdown files

03Polishing technical documentation before a major release or deployment

Key Features

01Interactive fix application via individual review or batch updates

022 GitHub stars

03Detection of terminology and structural inconsistencies

04Automated documentation auditing for style and grammar

05Support for directory-wide or file-specific reviews

06Seamless integration with Claude's Edit tool for direct file modification

Use Cases

01Ensuring consistency in style and terminology across a large documentation site

02Automatically correcting grammar and formatting errors in Markdown files

03Polishing technical documentation before a major release or deployment