i-doc-final-check

Name: i-doc-final-check
Availability: InStock
Author: kamo

Enforce documentation completion criteria and issue states before PRs.

12|1|Updated Dec 27, 2025

Search Tags:#workflow #verification #docs #issue-tracking #pr-review #gatekeeping #documentation-maintenance

Ready to run

npx skills add https://github.com/apokamo/kaji --skill i-doc-final-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i-doc-final-check
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/i-doc-final-check
Command: npx skills add https://github.com/apokamo/kaji --skill i-doc-final-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs the final validation for docs-only workflows, ensuring document consistency and correct Issue states before a PR proceeds.

Core Features & Use Cases

Validate docs alignment with current standards and cross-reference correctness.
Update and reflect Issue statuses in PR discussions based on verification results.
Gate PRs in the docs-maintenance workflow to ensure releases meet documentation quality criteria.

Quick Start

Run the i-doc-final-check to verify docs readiness and update issue status before merging.

Frequently Asked Questions about i-doc-final-check

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

FAQPage Schema

How do I enforce documentation completion criteria before a PR is merged?▼

Docs PR readiness validation checks cross-reference correctness, verifies issue state alignment, and enforces documentation maintenance standards to gate pull requests before merging.

How do I validate cross-references and links in documentation maintenance workflows?▼

Cross-reference validation in docs maintenance is handled by programmatically verifying link alignment and document consistency, ensuring all references meet defined standards before a pull request advances.

Can I automatically update issue tracking states based on PR verification results?▼

Yes, issue tracking states are updated and reflected in PR discussions automatically based on the results of your documentation verification and cross-reference checks.

What is the best way to gate pull requests for docs-only changes?▼

Gating pull requests for docs-only changes requires applying programmatic enforcement of completion criteria, verifying document alignment and issue statuses to ensure releases meet documentation quality standards.

Does this docs PR review pipeline require any external dependencies?▼

No external dependencies are required to run this gatekeeping verification process, as it operates autonomously to validate docs alignment and issue tracking states within your workflow.