This skill provides the procedures and knowledge for converting fragments of code and logs into "material" for blog posts and documentation. It objectively observes the development process and uncovers the story behind it.
When to Use
- When you want to look back on what you did at a break in development work and look for ideas for output.
- When you want to reconstruct the intent behind a complex fix from Git history or chat logs.
- When you want to create an "accurate collection of material based on facts" for technical reports, weekly reports, PR descriptions, etc.
Core Features
1. Repository Archaeology
- Git Analysis: Read recent commit messages, diffs, and PR descriptions, and extract the key points of technical changes.
- Documentation Integration:
ARCHITECTURE.mdやCHANGELOG.mdand link the overall picture of the project with individual changes.
2. Insight Extraction
- Record of Decisions:
task.mdやimplementation_plan.mdto identify why that approach was chosen and what alternatives existed. - Challenges and Solutions:
walkthrough.mdand error logs to find the "climaxes" of the challenges faced and how they were overcome.
3. Material Collection Generation (Output Generation)
Output a "collection of material for an article" that includes the following items.
- Background: Why this feature/fix was needed.
- Technical Details: What technology stack was used and what kind of implementation was done.
- Learnings: The knowledge and difficulties gained through development.
Workflow
- Environment Exploration:
git logand the project directory to identify highly relevant files and history. - Organizing Facts: Organize events chronologically or by theme (feature additions, bug fixes, design changes).
- Storyization: Rather than merely listing history, extract the framework of a story: "challenge → trial and error → solution."
- Output of Material: Output in Markdown format a collection of material for a blog, documentation, or for humans to read.