document-history

You can generate a changelog entry from git history by invoking the skill without arguments; it automatically detects the work type and title from recent commits to populate structured documentation templates with relevant session details.

The best way to document completed development sessions is by generating structured history documents from templates that automatically capture contextual details for features, bug fixes, implementations, and migrations to ensure consistent record-keeping.

Yes, you can use session context to populate documentation templates for code migrations; the skill automatically fills all template sections with relevant information from the current development session and git history.

Yes, the document-history skill works without manual arguments by automatically detecting the type and title from git history, seamlessly populating all template sections with the current session context.

To create structured work history docs for a recent implementation, use the skill to generate a comprehensive document from a template, automatically filling in the description, problem solved, and relevant technical details.