code-review-intent

Draft design intent documents from briefs and code diffs.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-intent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-intent
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/code-review-intent
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-intent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps leaders and teams quickly generate a formal design intent document capturing requirements, decisions, trade-offs, and intentional exclusions from a concise work brief and code diffs.

Core Features & Use Cases

  • Structured Design Intent: Create a clear, publishable design intent document from a brief and diffs.
  • Decision Justification: Capture key design choices and rationale for future reference.
  • Use Case Scenarios: Produce a ready-to-review artifact for PRs, handoffs, and audits.

Quick Start

Write a design intent document for the current feature branch using the provided brief and git diff, and save it to the designated path.

Frequently Asked Questions about code-review-intent

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

FAQPage Schema
How do I document design intent from a git diff for a PR?

Draft design intent documents from concise briefs and code diffs to capture requirements, design decisions, and trade-offs. This skill applies to feature branches during PR preparation, reviews, and handoffs where clear intent documentation is required.

What is the best way to capture design decisions and trade-offs before a handoff?

Capture design decisions and trade-offs by generating a formal design intent document from a work brief and code diffs. This creates a ready-to-review artifact that justifies key design choices for future reference during audits and handoffs.

How do I generate a design intent document for my feature branch?

Generate a design intent document by providing a brief and the git diff for your feature branch. The skill enforces a YAML frontmatter with name and description, saving the artifact to the designated path within your review-artifacts directory.

Does the design intent document include a summary of discussion points?

Yes, the design intent document includes a concise set of discussion points and a summary. It captures requirements, intentional exclusions, and design rationale to produce a ready-to-review artifact for PRs and handoffs.

Can I use this skill to prepare artifacts for code reviews and audits?

Yes, you can use this skill to produce ready-to-review artifacts for PRs, handoffs, and audits. It drafts a structured design intent document capturing your requirements, decisions, and trade-offs from the provided brief and diffs.

What format does the generated design intent document use?

The generated design intent document uses a YAML frontmatter containing the name and description, outputting a markdown file. It is saved directly to the .codex/review-artifacts/{branch-name}/design-intent.md path.