i-doc-update

Automate documentation updates for docs-only issues with consistency checks.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill i-doc-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-doc-update
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/i-doc-update
Command: npx skills add https://github.com/apokamo/kaji --skill i-doc-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates documentation updates without touching code or tests, while ensuring alignment with the current implementation, CLI, and operation policies.

Core Features & Use Cases

  • Docs-only updates: restrict changes to documentation only, preventing unintended code or test changes.
  • Consistency checks: verify that documentation remains aligned with the actual implementation and workflow policies.
  • Guided workflow: supports issue-driven docs tasks from review-ready to final-check with built-in validation steps.

Quick Start

Run i-doc-update on a docs-only issue to apply approved documentation changes.

Frequently Asked Questions about i-doc-update

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

FAQPage Schema
How do I automate documentation updates without modifying code or tests?

You can automate documentation updates by running a docs-only workflow on an issue, which restricts changes to documentation files and prevents unintended code or test modifications.

What is the best way to ensure documentation consistency with current implementation?

To ensure documentation consistency with current implementation, use structured validation checks that verify factual accuracy, implementation alignment, and operational integrity against workflow policies.

How do I manage issue-driven documentation maintenance tasks end to end?

Managing issue-driven documentation maintenance requires a guided workflow with built-in validation steps, supporting tasks from review-ready stages through final-check validation to ensure operational integrity.

Does this docs maintenance approach work for verifying operational integrity and workflow policies?

Yes, this docs maintenance approach works for verifying operational integrity by implementing structured reviews and validation commands that ensure documentation aligns with current workflow policies.

Can I apply documentation changes to docs-only issues without touching the codebase?

Yes, you can apply documentation changes to docs-only issues without touching the codebase, as the workflow specifically restricts modifications to documentation and ensures alignment with the actual implementation.

What are the limitations of using a docs-only update workflow for issue management?

The limitation of a docs-only update workflow is that it strictly restricts changes to documentation only, meaning it cannot be used for issues requiring code changes, test updates, or functional implementation modifications.