achievements

Generate grouped bullet-point change summaries for the current branch.

3|3|Updated Aug 19, 2025
One-click install
npx skills add https://github.com/StartaleGroup/app-sdk --skill achievements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: achievements
Source: https://github.com/StartaleGroup/app-sdk/tree/main/.claude-lib/shared/skills/achievements
Command: npx skills add https://github.com/StartaleGroup/app-sdk --skill achievements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface a clear, grouped summary of all changes made on the current branch compared to its fork point, saving review time and preventing missed updates.

Core Features & Use Cases

  • Group-by-change: Collate commits into single bullets per feature or fix.
  • Branch-awareness: Focuses on this branch only, ignoring unrelated history.
  • Use Case: When preparing a pull request, generate an at-a-glance list of what changed since rebase or fork.

Quick Start

Ask the tool to display a grouped bullet-point achievements list for the current branch.

Frequently Asked Questions about achievements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize branch changes before creating a pull request?

To summarize branch changes for a pull request, you can generate a grouped bullet-point list of all commits since the branch diverged from its fork point. This provides a concise, feature-oriented changelog for reviewers.

What is the best way to group git commits by feature for a changelog?

Grouping git commits by feature involves collating related commits into single bullets per feature or fix. This approach focuses on the current branch only, ignoring unrelated history to produce a clear summary.

Can I generate a development summary that only shows diff changes from the fork point?

Yes, you can generate a development summary that identifies the current branch and reports only the diff changes from its fork point. It outputs a structured list of changes along with file and commit counts.

How do I get a concise file and commit count report for my current git branch?

Getting a concise file and commit count report requires analyzing the current git branch against its fork point. The output provides a structured list of grouped changes alongside the exact file and commit counts.

Does this branch summary tool work with local development branches?

Yes, this branch summary tool works with local development branches. It identifies the current local branch and surfaces a clear, grouped summary of all changes made since diverging from the fork point.