Generate a branch-tagged architectural history report in BRANCH_HISTORY.md.
npx skills add https://github.com/0xxmemo/litellmctl --skill branch-history
Please help me install this Agent Skill. Skill: branch-history Source: https://github.com/0xxmemo/litellmctl/tree/main/skills/branch-history Command: npx skills add https://github.com/0xxmemo/litellmctl --skill branch-history
Generates a regenerable BRANCH_HISTORY.md at the repository root that explains the current git branch's state from its divergence with the base to HEAD, organized into Start, Mid, and End sections. It tags the file to the active branch so switching branches prompts a regeneration when invoked on a different branch.
Run the branch-history skill to generate a fresh BRANCH_HISTORY.md for the current branch.
High-intent search queries and answers about installing and using this skill.
To generate a changelog from a git branch divergence point, you need a tool that computes the merge-base and reads git logs to build a narrative history. This skill automates that process by regenerating a BRANCH_HISTORY.md file from the base to HEAD.
Documenting feature branch architecture for code reviews is best handled by generating a structured report that captures changes from the divergence point. This skill creates a BRANCH_HISTORY.md file organized into narrative sections to provide a readable architectural audit trail.
You can automatically track git branch history for onboarding by regenerating a markdown file on each invocation. This skill tags the document to the active branch and recomputes the full history using git commands to reflect the latest repository state.
The branch history report does not update automatically on its own, but switching branches prompts a regeneration when the skill is invoked. It uses an HTML-comment header to tag the document to the current branch, ensuring the narrative matches the active context.
Creating a readable architectural history from a git merge-base involves capturing diffs and logs between the base and HEAD. This skill computes the divergence using git commands and writes the results into a structured markdown file for architectural audits.
You need to regenerate a branch history markdown file whenever the current branch diverges further or when switching to a different branch. Because the skill recomputes from scratch on every run, invoking it ensures the architectural narrative reflects the latest commits.
kage1020Analyze branch changes and generate a five-section Markdown diff report.
cosmicstack-labsTurn scattered internal documentation into a structured, searchable wiki.
Kushal9889Update the CHANGELOG and create a version tag in Git.
dennisonbertramGenerate release notes from Git history using Conventional Commits and git-cliff.
