Agent skill · writing content · github
brag-sheet
Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.
Why this skill is useful
Adds a structured method for generating evidence-backed impact statements that the AI wouldn't reliably create on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Brag Sheet — Work Impact Writer Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs, git history, and PRs to reconstruct forgotten work. USE FOR: "brag", "log work", "what did I do", "backfill", "performance review", "self-review", "promo packet", "weekly update", "status report", "write impact statement", "what did I ship", "I forgot to log my work", "review prep", "accomplishments" DO NOT USE FOR: project management, sprint planning, time tracking, ticket creation Quick Start User wants... Mode Output --------------- ------ -------- Log one accomplishment Capture 1 impact-first entry "What did I do last week?" Backfill Entries grouped by week, mined from git/PRs/sessions Prep for review or promo Review Pack Entries grouped by impact theme + STAR narratives Agent Behavior Rules 1. DO confirm the time range and scope before scanning sources. Don't assume "last week" — ask. 2. DO check which tools are available (savetobragsheet, git, gh) before choosing a workflow. 3. DO always include all three parts: action → result → evidence. If evidence is missing, write (evidence needed) — never silently omit. 4. DO show drafted entries to the user before saving. Never auto-save without confirmation. 5. DO group related commits into a single entry. Ten commits on the same feature = one entry. 6. DO preserve the user's voice. Reframe for impact, but don't invent accomplishments or inflate scope. 7. DO NOT fabricate metrics, team sizes, or impact numbers. If the user doesn't provide a number, don't invent one. 8. DO NOT write entries for work the user only described verbally without verifying. Ask: "Did this ship? Is there a PR or doc I can reference?" 9. DO NOT skip the backfill scan steps or draft entries before scanning is complete. 10. DO NOT pad weak periods with trivial entries. An honest gap is better than inflated fluff. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/brag-sheet