dev-reports

Route report requests to templates and render Markdown outputs.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-reports
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-reports
Source: https://github.com/mpazaryna/claude-toolkit/tree/main/generated-skills/dev-reports
Command: npx skills add https://github.com/mpazaryna/claude-toolkit --skill dev-reports

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the friction of documenting development work by automatically generating structured reports from your commit history or manual input.

Core Features & Use Cases

  • Git Journal: Summarize coding sessions into structured entries with decisions, files changed, and next steps.
  • Multiple Formats: Create devlogs, status updates (22A/22B), and progress reports tailored to different audiences.
  • Use Case: After a 4-hour refactoring session, use this Skill to automatically generate a comprehensive journal entry that captures your technical decisions and progress.

Quick Start

Use the dev-reports skill to journal today's work from git commits.

Frequently Asked Questions about dev-reports

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

FAQPage Schema
How do I generate development reports from git commits?▼

Generate development reports by routing git history through dev-reports templates for journals, devlogs, or status updates. The Skill automatically extracts commit data, applies structured formatting with required sections, and saves outputs as Markdown files to docs/journal/ or as form documents.

Can I create status updates and journals from git history automatically?▼

Yes. Dev-reports transforms git commits into structured journal entries and status updates (22A/22B forms) automatically, capturing technical decisions, files changed, and next steps without manual transcription.

What's the best way to document a coding session without writing from scratch?▼

Use git commit history as input to dev-reports templates. After a session, the Skill generates comprehensive documentation with decisions, changes, and progress captured directly from your commits, eliminating manual documentation effort.

Does dev-reports support multiple report formats?▼

Yes. Dev-reports supports Git Journals, Devlogs, and business status updates (22A/22B). Each format routes through separate templates and saves to appropriate file paths with distinct structures for different audiences.

Can I use dev-reports when git history isn't available?▼

Yes. Dev-reports accepts manual input for narrative summaries and business reports when git history is unavailable, routing requests to appropriate templates and rendering formatted Markdown output.

What output formats does dev-reports generate?▼

Dev-reports generates timestamped Markdown files (YYYY-MM-DD-HHMM-slug.md) for journals and Devlogs, plus structured forms (FORM-22-A.md, FORM-22-B.md) for status updates, all saved to docs/journal/ with required sections.