// Developer reporting skill for work documentation and communication. Use when writing journals, devlogs, status updates (22A/22B), progress reports, or documenting development work. Generates reports from git history or manual input.
| name | dev-reports |
| description | Developer reporting skill for work documentation and communication. Use when writing journals, devlogs, status updates (22A/22B), progress reports, or documenting development work. Generates reports from git history or manual input. |
Document and communicate development work. From git commits to polished reports.
This skill supports multiple report formats:
| Type | When to Use | Trigger Phrases |
|---|---|---|
| Git Journal | Summarize work from commits | "journal this", "journal today's work" |
| Devlog | Narrative work documentation | "devlog", "write a devlog" |
| Status (22A) | Full Progress/Plans/Problems | "22A", "PPP update", "full status" |
| Status (22B) | Condensed status update | "22B", "quick status" |
examples/:
examples/github-journal.mdexamples/devlog.mdexamples/form-22a.mdexamples/form-22b.md| Request | Template |
|---|---|
| "Journal this", "journal the last 4 hours" | examples/github-journal.md |
| "Write a devlog", "devlog update" | examples/devlog.md |
| "22A", "PPP update", "progress report" | examples/form-22a.md |
| "22B", "quick status" | examples/form-22b.md |
Generates structured journal entries from git commit history. Great for:
Narrative-style work logs with context and decisions. Great for:
Structured Progress/Plans/Problems format. Great for:
| Skill | Purpose |
|---|---|
dev-inquiry | Technical investigation and decision-making |
dev-reason | Problem-solving and debugging (future) |
dev-reports | Work documentation and communication |