Brag Doc From Git

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

Git & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add agentkitco/agentkit-dev-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add agentkitco/agentkit-dev-skills --skill brag-doc-from-git
Manual install
git clone --depth 1 https://github.com/agentkitco/agentkit-dev-skills.git /tmp/agentkit-dev-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agentkit-dev-skills/skills/brag-doc-from-git ~/.claude/skills/brag-doc-from-git

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Brag document from git history

Goal: turn what you actually shipped into a draft you can edit, without inventing impact. A brag document lists work and results; this skill collects the work and marks every missing result as a gap for you to fill.

## Step 1: collect the evidence

Ask for the time window (default: the last 6 months) and the repositories. Then, with the GitHub CLI signed in:

```
gh search prs --author @me --merged --merged-at ">=YYYY-MM-DD" --json title,url,closedAt,repository --limit 200
```

For code not on GitHub, use `git log --author="<name or email>" --since="YYYY-MM-DD" --no-merges --pretty="%h %ad %s" --date=short` in each repository. Also ask the user to paste anything git cannot show: incidents handled, mentoring, reviews done, talks, docs, on-call, design decisions, kind words from colleagues.

Do not read private repositories the user did not name. Do not guess names, teams or numbers.

## Step 2: group, do not summarize yet

Group the items into themes (for example: reliability, new features, performance, tooling, mentoring, cross-team work). List each item under its theme with date and link. Merge duplicates (a feature PR plus its follow-up fixes).

## Step 3: draft each theme

For every theme write:

- **What I did**: one or two sentences in plain verbs, using only what the titles, diffs and user notes support.
Read the full skill on GitHub

Details

Skill name
brag-doc-from-git
Path
skills/brag-doc-from-git/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Brag Doc From Git skill do?

Build an evidence-based brag doc or self-review draft from your merged PRs and commits, leaving visible gaps where results are unknown. Use for review season, promotion cases or resumes.

How do I install the Brag Doc From Git skill?

Claude Code plugin: /plugin marketplace add agentkitco/agentkit-dev-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Agents Md Audit

agentkitco/agentkit-dev-skills

Audit an AGENTS.md, CLAUDE.md, Cursor rule or Copilot instructions file for stale commands, broken paths, vague rules, secrets and contradictions. Use to review or trim agent instructions.

AI, LLMs & AgentsIn 1 list

Dependency Upgrade

agentkitco/agentkit-dev-skills

Upgrade one dependency at a time by reading its changelog, planning for breaking changes, updating code and proving it still builds and passes. Use to bump, update or migrate a package.

Git & Code ReviewIn 1 list

Explain Codebase

agentkitco/agentkit-dev-skills

Map an unfamiliar repo covering purpose, entry points, how to run it, main modules, data flow and risky areas, with file references. Use when asked to explain or onboard onto a codebase.

Software DevelopmentIn 1 list

Report

danybgoode/golden-frijoles

Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a metrics sheet. Use when the product owner asks to "post the standup", "run the daily standup", "what ha

Git & Code ReviewIn 1 list

PR Description

agentkitco/agentkit-dev-skills

Write a pull request title and description from the actual diff and commits, with what changed, why, how it was tested and what to review. Use when asked to write or improve a PR description.

Git & Code ReviewIn 1 list

Build Order Sync

danybgoode/golden-frijoles

Regenerates Roadmap/00-ideas/BUILD-ORDER.md when it has drifted from the SSOT (each epic README's frontmatter status:) and opens a claude/ docs PR with the fix — never hand-edits the board. Use when the product owner asks to "sync the build order", "regenerate BUILD-ORDER.md", "check board drift", "is the build-order board stale", "open a build-order PR", or as the nightly ops routine's first step. Runs scripts/build-order-sync.mjs, which does the check, the regen, and (on real drift) the branch/commit/ push/PR — this skill just invokes it and reports the result.

Git & Code ReviewIn 1 list

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.