whatisgithub

What is brag-doc?

deeheber/brag-doc — explained in plain English

Analysis updated 2026-05-18

13Audience · developerComplexity · 1/5Setup · easy

In one sentence

A Claude Code template that turns a couple minutes of daily win logging into ready-to-edit promotion and review drafts.

Mindmap

mindmap
  root((brag-doc))
    What it does
      Daily win logging
      Review draft generation
    Skills
      daily-eval
      review-builder
    Formats
      Generic portable
      Company specific
    Privacy
      Fictional sample data
      Use a private repo

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Log a couple minutes of daily accomplishments in Claude Code

USE CASE 2

Generate a self review draft from months of logged entries

USE CASE 3

Build a promotion case formatted to match your employer's actual review questions

USE CASE 4

Keep a private, dated record of your work impact over time

What is it built with?

Claude CodeMarkdown

How does it compare?

deeheber/brag-doc09catho/axon0x1-1/revival
Stars131313
LanguageJavaScriptC++
Setup difficultyeasymoderatehard
Complexity1/54/55/5
Audiencedeveloperresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires Claude Code, move real entries to a private repo since logged data includes real names and feedback.

So what is it?

brag-doc is a template repository built around two Claude Code skills that help an engineer keep track of their own accomplishments so review season is not a scramble to remember what happened months ago. The idea is to log daily wins in a couple of minutes, then turn those entries into a promotion case or self review draft when it is actually needed. It works in two steps. The daily eval skill, triggered with a slash command or just by saying something like let's log today's wins, asks a few quick questions and appends the answers to a dated markdown file under entries, organized by year and month. Entries are append only, so someone can log more than once a day or backfill a specific past date. The review builder skill then reads through those entries and generates a draft, either in a generic portable format or in a format that mirrors a specific employer's actual review questions, landing in a reviews folder that is not committed to git. The generated draft is meant to be read over and edited before submitting, since it can only be as complete as what was actually logged. Setting up the company specific format means swapping in your own employer's real review questions in place of the fictional example the repo ships with, optionally by dropping in a PDF of the official template and asking Claude to update the format to match it. The sample entries and sources included in the repo are entirely fictional, describing a made up company and made up people, purely to demonstrate the workflow. Because this is a public template, the README is explicit that once someone starts logging their own real work, those entries will contain real names and real manager feedback, and recommends moving to a private repository rather than pushing that real journal to a public one. The only requirement to use it is having Claude Code installed, since both skills live entirely inside this repo's .claude/skills folder and produce plain markdown as output.

Copy-paste prompts

Prompt 1
Set up brag-doc in a private repo and help me log today's wins using the daily-eval skill.
Prompt 2
Run the review-builder skill in generic format for my entries from last quarter.
Prompt 3
Help me update the company review format using the template PDF I dropped in sources/.
Prompt 4
Explain the difference between the generic and company review-builder tracks in this repo.

Frequently asked questions

What is brag-doc?

A Claude Code template that turns a couple minutes of daily win logging into ready-to-edit promotion and review drafts.

How hard is brag-doc to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is brag-doc for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.