i-dev-final-check

Automate final-check phase verification for pull-request progression prerequisites.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the dev workflow's final-check phase to verify that all prerequisite traces, design updates, and issue updates are complete before a PR can progress.

Core Features & Use Cases

  • Collects and validates design promotion, documentation updates, and issue status across implement/review-code/final-check paths.
  • Enforces quality gates and evidence consolidation to ensure PR readiness in automated workflows.
  • Use Case: When a code change passes initial reviews, this skill ensures all required checks are satisfied and the PR is ready to merge.

Quick Start

Run the final-check to verify you are ready to advance the PR to the next stage.

Frequently Asked Questions about i-dev-final-check

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

FAQPage Schema
How do I automate final checks before a pull request can progress?

Automating final checks enforces quality gates and gathers evidence to ensure prerequisite artifacts and approvals are complete before PR progression. This validates design updates and issue statuses across implement and review paths.

What is a dev workflow final-check phase for pull request readiness?

A dev workflow final-check phase validates that prerequisite traces, design updates, and issue updates are complete. It consolidates evidence and enforces quality gates to ensure PR merge readiness.

How do I enforce quality gates and evidence consolidation in an automated dev workflow?

Enforcing quality gates in an automated dev workflow gathers evidence across implement, review-code, and final-check steps. It validates design promotion and documentation updates to generate PR readiness verdicts.

Does the final-check process integrate with issue tracking and issue-body changes?

Yes, the final-check process integrates with issue tracking by performing issue updates, adding notes, and applying issue-body changes. This ensures issue statuses accurately reflect PR progress.

When do I need to perform design promotion and documentation updates for a code change?

Design promotion and documentation updates are needed when code changes pass initial reviews. The final-check phase collects and validates these updates to ensure required checks are satisfied before merging.

Why does my pull request fail to progress after passing initial code reviews?

A PR may fail to progress if prerequisite artifacts, design updates, or issue updates are incomplete. The final-check phase enforces quality gates to verify all required evidence is consolidated before advancing.