2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill commit-poetry- _meta.json282 B
- SKILL.md8.7 KB
Overview
This skill transforms git history into crafted poetry, turning commit messages, branches, and file histories into haiku, sonnets, limericks, ballads, free verse, and more. It highlights the shape of your work—bugfixes, incidents, migrations, and releases—by matching poetic form to event type. Use it to make retrospectives memorable, lighten postmortems, or celebrate releases with creativity.
How this skill works
The skill inspects commit metadata (messages, timestamps, authors), branch ranges, file history, and tags to classify the nature of each change. It applies predefined poetic templates and syllable/line rules to convert commit sequences into the appropriate form (haiku for small fixes, sonnet for sprints, ballad for big rewrites, etc.). Output is plain text poetry ready for sharing in changelogs, retros, or team chat.
When to use it
- Sprint retrospectives — present two-week histories as sonnets instead of slides
- After production incidents — generate free verse sequences for incident timelines
- Release celebrations — produce rap verses or ballads for release notes
- File archaeology — turn long file histories into Gothic horror or epics
- Friday or team morale moments — random limericks and limerick rounds
- Merge conflicts or opposing PRs — dramatize resolutions as dialogue
Best practices
- Run locally against a cloned repository to avoid exposing private logs
- Choose the Poetry Mode that matches the scope (Last Commit, Last Sprint, Release, etc.)
- Review and optionally edit generated poems before sharing with stakeholders
- Use sonnets/ballads for summaries and haiku/limericks for individual commits to keep reading concise
- Include the original commit references or short diffs when using poems for documentation
Example use cases
- Turn the last sprint’s commits into a sonnet for a retro presentation
- Create a free verse timeline of an on-call incident for postmortems
- Convert a legacy module’s file history into a Gothic horror piece for context before refactoring
- Celebrate a major release by generating a rap verse for the team channel
- Produce limericks from small fixes for an end-of-week team newsletter
FAQ
No. It works locally with your git repository and has no external dependencies or API calls.
Can I customize the poetic rules or templates?
Yes. Templates and mappings from commit types to poetic forms are configurable so teams can tune tone and length.