Results for “git-history”
14 skillswiki-changelog
Analyzes git commit history and generates structured changelogs categorized by change type.
2.7k
repo-story-time
Transform any repository's commit history and structure into a comprehensive technical summary and narrative story.
36.2k
changelog-generator
Transforms technical git commits into polished, user-friendly changelogs by analyzing commit history, categorizing changes, and generating customer-ready release notes.
66.9k
app-store-changelog
Generate user-facing App Store release notes by collecting and summarizing user-impacting changes from git history since the last tag.
3.8k · bundle
doc-maintenance
Audits top-level documentation against recent git history to detect drift, applies minimal edits, and opens a pull request.
20 · bundle
brag-sheet
Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates by mining Copilot CLI session logs, git history, and GitHub PRs.
36.2k
More results
suggest-awesome-github-copilot-instructions
Suggests relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions and identifying outdated ones.
36.2k
git-workflow
Learn Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
226k
release-notes
Drafts a changelog entry from local git history between two refs, matching the project's existing changelog format, and writes it to a draft file.
0
changelog
Generates a single unified changelog from git history, written in plain language for the whole company, defaulting to Slovak and comparing the release branch against develop for unreleased changes.
2
changelog
Generates or updates CHANGELOG.md from git history, parsing conventional commits, grouping by version tags, and formatting into keep-a-changelog sections with comparison links.
13
retro
Engineering retrospective — generates a data-driven report of development velocity, commit patterns, hotspots, and team insights from git history. Saves results for week-over-week comparison.
8
em-dash
Provides guidance on the history and correct usage of the em dash, enforcing a strict policy of never using em or en dashes in code or data files, and replacing them with hyphens. Also covers general punctuation rules for code comments.
36.2k
maintaining-documentation
Maintains a product repo's canonical docs structure (CLAUDE.md, progress.txt, docs/product+system+design-system, context/) as single source of truth, and keeps the log.md session history separate from the progress.txt state snapshot. Trigger after feature completion, before git push, on architecture changes, at session end, or explicit "update docs"/"sync documentation" requests. Skip for trivial changes (<10 LOC, no logic/schema/UI changes).
3