brag-sheet

Generates evidence-backed impact statements from git commits, GitHub PRs, and Copilot CLI session logs.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill brag-sheet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brag-sheet
Source: https://github.com/github/awesome-copilot/tree/main/skills/brag-sheet
Command: npx skills add https://github.com/github/awesome-copilot --skill brag-sheet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often forget what they accomplished when performance reviews or promotion packets come due, and reconstructing months of work from memory produces vague, weak entries. This Skill mines git history, merged PRs, and Copilot CLI session logs to rebuild your work record and rewrites it as impact-first statements with evidence.

Core Features & Use Cases

  • Backfill Work History: Scans git commits, GitHub PRs, and Copilot session logs to reconstruct forgotten work grouped by week.
  • Impact-First Entries: Enforces a strict action → result → evidence contract, marking gaps as "(evidence needed)" instead of fabricating metrics.
  • Review Prep Mode: Selects top accomplishments, organizes them by impact theme, and rewrites them as STAR narratives for performance reviews or promotion packets.
  • Use Case: Ask "what did I do last half?" and receive categorized markdown entries with PR links and quantified outcomes ready to paste into a self-review.

Quick Start

Ask the agent to backfill your work history for the last two weeks using git commits and merged PRs, then draft impact statements for your review.

Frequently Asked Questions about brag-sheet

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

FAQPage Schema
How do I reconstruct what I worked on for a performance review?

Run the backfill workflow, which scans your git commits, merged GitHub PRs via the gh CLI, and Copilot CLI session logs for a stated time range. Related work is grouped into single entries and rewritten as impact-first statements with evidence links.

How to write impact statements from git commits?

Group related commits on the same feature into one entry, then frame it as action → result → evidence, such as a PR number or metric. Ten commits on one feature become a single entry with the highest-impact framing, not ten separate lines.

Does the brag-sheet skill require git or GitHub CLI?

No, it works standalone with zero dependencies. Git and the gh CLI are optional sources for backfilling; if neither is available, the skill falls back to a guided interview about what you worked on and who benefited.

What if I cannot quantify the impact of my work?

Not every entry needs a metric. The evidence ladder accepts PR links, observable outcomes like unblocking a team, or qualitative results with context. The skill never invents numbers and marks missing proof as "(evidence needed)".

Why does backfill show no recent commits for my review period?

You may work across multiple repos or the review period may span 6-12 months. Use gh pr list --author @me --state merged for cross-repo history and set explicit --since and --until dates on git log for long ranges.