code-report

Generate structured Korean software change reports from development workflow artifacts.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dmlguq456/agent_setting --skill code-report-dmlguq456
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-report
Source: https://github.com/dmlguq456/agent_setting/tree/main/adapters/claude/skills/code-report
Command: npx skills add https://github.com/dmlguq456/agent_setting --skill code-report-dmlguq456

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms complex software development artifacts into clear change reports, reducing the effort required to understand completed engineering work and decisions.

Core Features & Use Cases

  • Pipeline Report Generation: Synthesizes plans, development logs, reviews, tests, and decisions into structured engineering reports.
  • Insight Extraction: Highlights why changes were made, their impact, design principles, and future considerations instead of only listing modifications.
  • Use Case: A development team can use this Skill after a coding cycle to produce a Korean-language report that documents deliverables, quality checks, and architectural insights.

Quick Start

Generate a change report from the completed coding plan and associated workflow artifacts.

Frequently Asked Questions about code-report

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

FAQPage Schema
How do I generate a software change report from development workflow artifacts?

To generate a software change report, you provide completed coding plans, implementation logs, and test records as input artifacts. The system synthesizes these workflow records into a structured engineering summary.

What is included in an engineering documentation synthesis for completed code cycles?

An engineering documentation synthesis includes deliverables, quality checks, and architectural insights extracted from development logs. It highlights why changes were made, their impact, and design principles instead of only listing modifications.

Can I use code review and test artifacts to create a Korean-language engineering report?

Yes, you can use code review and test artifacts to create a Korean-language engineering report. The process requires artifact resolution and multi-source analysis to reconcile implementation decisions into actionable Korean summaries.

What's the best way to document design principles and implementation decisions from a coding cycle?

The best way to document design principles and implementation decisions is by analyzing multi-source workflow artifacts. This extracts insights into why changes were made and reconciles technical documentation into actionable summaries.

Does automated change analysis require completed development logs and technical documentation?

Yes, automated change analysis requires completed development logs and technical documentation as input. It relies on resolving these engineering records to perform multi-source analysis and generate structured software change reports.