stn.
Get Started Free

Brag, export & graph

Generate a brag doc, export your data as Markdown, and read the context graph — the connective tissue between your work and your codebase.

Brag docs

stn brag                          # a Markdown brag doc for the last month
stn brag --period weekly          # weekly | monthly | quarterly (7 / 30 / 90 days)
stn brag --from YYYY-MM-DD --to YYYY-MM-DD --team TEAM
stn brag --no-github              # don't include GitHub reviews + commits
stn brag --narrate                # rewrite your accomplishments into prose with AI

Generates a Markdown summary of your work over a period — shipped entries, decisions, blocks you cleared for others, and how many checkpoints you captured — for 1:1s and reviews. With gh installed it also lists the PRs you reviewed and the commits you authored in the range (review work a commit-only brag misses). --narrate rewrites your accomplishments into prose with AI; it's gated to paid accounts with AI draft-assist enabled, and the draft is yours to edit, never auto-shared.

Export

stn export TEAM                 # your entries in a team as Markdown (./stndp-export)
stn export TEAM ./my-folder     # choose the output directory (the 2nd argument)
stn export --me                 # export your private checkpoints instead (to ./stndp-export)

Writes one portable Markdown file per entry (or per checkpoint with --me), each with a small YAML front-matter header. Your context is yours to take with you; this is the bulk export of it.

Reading the graph

stn repos                         # the repos your work touches (the codebase axis)
stn repo REPO_ID                  # one repo: branches, the tracker projects it tracks, connected work
stn projects                      # the tracker projects (Jira/ClickUp/Monday/Linear/…) you can see
stn project PROJECT_ID            # one project: its work items and the repos that track it
stn files REPO_ID                 # browse a repo's file tree (repo root)
stn files REPO_ID --prefix app/billing   # list a sub-directory
stn file-context PATH             # what's known about a file: decisions, who touched it & why, linked PRs
stn file-context app/billing/services.py#charge --repo REPO_ID --limit 20

file-context accepts a file path, a directory (for the whole subtree's context), or path#symbol to narrow to a class or function. Omit --repo to match any repo you can see. Repos, files, and work items appear once you capture work with git context — via stn checkpoint or ambient capture.

Attach external work and walk connections:

stn link OBJECT_ID PROJ-123                 # attach a ticket/PR/url to an entry (default)
stn link OBJECT_ID https://github.com/org/repo/pull/42 --type checkpoint
stn link OBJECT_ID https://example.com/doc --type decision
stn graph neighbors decision 42            # what's connected to a node (entry | decision | checkpoint)
stn graph neighbors entry 7 --rel supersedes
stn graph path decision 42 --rel supersedes --depth 10   # walk a chain of one relation

link attaches a Jira key (PROJ-123), a PR url, or any url to an entry, checkpoint, or decision, so the graph can show live ticket/PR status next to the work it relates to (see Integrations). graph neighbors lists a node's edges and external links; graph path walks one relation (e.g. a decision's supersession history) up to --depth hops.