promoteme

A CLI that helps you write brag documents by analyzing your GitHub contributions.

Features

• Automatic PR fetching via GitHub CLI
• Repository grouping and analysis
• AI-powered document generation (Claude/Gemini)
• Multi-language output support
• Personal notes integration
• Date range filtering
• Organization and repository filtering

Prerequisites

• GitHub CLI (gh) installed and authenticated via gh auth login
• AI CLI for document synthesis:
  • Claude CLI (default)
  • or Gemini CLI

Installation

Via Cargo (crates.io)

cargo install promoteme

From source

git clone https://github.com/g4rcez/promoteme
cd promoteme
cargo install --path .

Usage

promoteme generate [OPTIONS]

Options:
  --start-date    Start date YYYY-MM-DD (default: 6 months ago)
  --end-date      End date YYYY-MM-DD (default: today)
  --org           Filter by organization(s), comma-separated
  --repo          Filter by repo(s), format: owner/repo
  -l, --language  Output language (English, Portuguese, etc.)
  -m, --model     AI model: claude (default), gemini. Use cli@model format for specific model.
  --notes         Directory with personal notes (.md/.txt)

Examples

Basic usage (last 6 months):

promoteme generate

With date filters:

promoteme generate --start-date 2024-01-01 --end-date 2024-06-30

Filter by organization:

promoteme generate --org my-company

Filter by specific repositories:

promoteme generate --repo owner/repo1 --repo owner/repo2

Output in Portuguese:

promoteme generate -l Portuguese

Using Claude instead of Gemini:

promoteme generate -m claude

Using specific model:

promoteme generate -m claude@claude-opus-4-5

Include personal notes:

promoteme generate --notes ~/my-notes

Tech stack

• Rust
• Github CLI - https://cli.github.com/
• Github MCP - https://github.com/github/github-mcp-server
• Linear MCP - https://linear.app/docs/mcp

What is a Brag Document?

A brag document is a running record of your professional accomplishments. It serves as a personal changelog of your work contributions.

When to use

• Performance reviews
• Promotion discussions
• Job interviews
• Salary negotiations
• Updating your resume

Tips for maintaining one

• Update it regularly (weekly or bi-weekly)
• Include quantifiable impact when possible
• Document both technical and non-technical contributions
• Keep it factual and specific

What to include

• Pull requests and code contributions
• Code reviews and mentoring
• Documentation improvements
• Bug fixes and incidents resolved
• Process improvements
• Cross-team collaboration
• Knowledge sharing and presentations

References

• https://jvns.ca/blog/brag-documents/
• https://www.reddit.com/r/webdev/comments/19dtf6r/why_a_brag_doc_is_indispensable/