docs-writer

Enforce documentation standards for Gemini CLI repositories.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/kloune/gemini_cli_claude --skill docs-writer-kloune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/kloune/gemini_cli_claude/tree/main/.gemini/skills/docs-writer
Command: npx skills add https://github.com/kloune/gemini_cli_claude --skill docs-writer-kloune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures documentation created for Gemini CLI is accurate, clear, and consistent with the current codebase, by enforcing project standards and contribution guidelines.

Core Features & Use Cases

  • Enforce writing, editing, and reviewing standards for docs in the repository.
  • Align documentation with the project's CONTRIBUTING.md and related standards.
  • Support teams in producing high-quality docs for changes, releases, and onboarding.

Quick Start

Review the repository documentation and propose edits to align with Gemini CLI documentation standards.

Frequently Asked Questions about docs-writer

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

FAQPage Schema
How do I enforce documentation standards for Gemini CLI repositories?

You can enforce documentation standards for Gemini CLI by applying consistent writing, editing, and review processes. This ensures all Markdown files and repository docs comply with project standards like CONTRIBUTING.md.

What is the best way to align repository docs with CONTRIBUTING.md guidelines?

Aligning repository docs with CONTRIBUTING.md requires reviewing existing Markdown content and proposing edits. Applying project-specific documentation standards ensures accuracy, clarity, and consistency across the codebase.

How do I review and edit Markdown files to match project documentation standards?

Reviewing and editing Markdown files involves checking content against the quota-limit-style-guide and project standards. This process enforces writing quality and ensures documentation accurately reflects the current codebase.

Does this documentation editing process apply to all Markdown files in the codebase?

Yes, the documentation editing process applies to all repository documentation tasks. It covers both dedicated /docs content and standard Markdown files distributed throughout the entire codebase.

Can I use these documentation standards for onboarding and release notes?

Yes, you can use these documentation standards for onboarding and release notes. The enforced writing and reviewing standards support teams in producing high-quality docs for changes and new releases.

Why does my Gemini CLI documentation lose consistency across different repository updates?

Documentation loses consistency when updates do not follow enforced writing and editing standards. Applying the quota-limit-style-guide and CONTRIBUTING.md processes during reviews maintains alignment with the current codebase.