edit-docs

Align KDoc comments and MkDocs documentation to maintain a single source of truth.

219|41|Updated Feb 21, 2024
One-click install
npx skills add https://github.com/proto-at-block/bitkey --skill edit-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-docs
Source: https://github.com/proto-at-block/bitkey/tree/main/app/ai-rules/skills/edit-docs
Command: npx skills add https://github.com/proto-at-block/bitkey --skill edit-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain a single source of truth for documentation by aligning code comments (KDoc) and MkDocs-driven docs, reducing drift and inconsistencies across a codebase.

Core Features & Use Cases

  • Enforces consistency between KDoc and MkDocs documentation and references patterns and layouts.
  • Guides updating, consolidating duplicates, and ensuring accuracy across multiple modules.
  • Use Case: When a new API surface is added, update both KDoc and MkDocs to reflect current behavior and architecture.

Quick Start

Update KDoc and MkDocs to reflect the latest API changes across modules in one pass.

Frequently Asked Questions about edit-docs

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

FAQPage Schema
How do I keep KDoc and MkDocs documentation consistent across multiple modules?

To maintain consistent KDoc and MkDocs documentation, edit both simultaneously to reflect current API behavior. This enforces a single source of truth, reducing drift and ensuring references stay up-to-date across modules.

What is the best way to update documentation when adding a new API surface?

The best way to update documentation for a new API surface is to consolidate duplicates and edit both KDoc and MkDocs together. This enforces documented patterns, ensuring accuracy and coherence across mobile and backend components.

How does enforcing a single source of truth reduce documentation drift?

Enforcing a single source of truth reduces documentation drift by aligning KDoc and MkDocs layouts and patterns. It guides updates and consolidates duplicates, preventing inconsistencies across codebases with mobile and backend components.

Can I use this approach for projects spanning both mobile and backend components?

Yes, you can align documentation for projects spanning both mobile and backend components. The process enforces consistent KDoc and MkDocs patterns, ensuring cross-linking and non-duplication across diverse software modules.

How do I consolidate duplicate documentation across code comments and MkDocs?

To consolidate duplicate documentation, edit KDoc and MkDocs together to reflect the latest API changes. This enforces non-duplication and ensures accuracy by maintaining a single source of truth across all references.