What it produces:

• Project type and target audience classification
• An editorial score (how much content potential this project has)
• One ready-to-post content piece based on the project arc

When to use it:

When you want to explain the whole project to an audience, not just what you shipped today. Use it for launch posts, introduction threads, and "what is this thing I've been building" content.

Input options:

• Full history (default)
• Last 30, 60, or 90 days (Pro: date range selector)
• By release or tag (Pro)

Format:

Free tier: Trace picks the best format for your project.
Pro tier: Choose from all five formats before generating.

How it works:

1. Click any commit in your repo dashboard to evaluate it
2. Trace classifies the commit into one of the six story patterns
3. A verdict score from 1 to 5 is assigned
4. Commits scoring 3 or above unlock the Create Content button
5. Click Create Content to generate a ready-to-post piece from that commit

Why some commits don't unlock content:

Version bumps, typo fixes, config changes, and dependency updates score low (1–2) and do not produce the Create Content button. This is intentional. Trace is an editor. It tells you when not to post.

The honest documentation of what's hard. Debugging a gnarly bug at 2am, rethinking an architecture, shipping something that broke in production. Readers trust founders who show the difficulty, not just the win.

The moment something goes live. A feature, a fix, a redesign, a first deploy. Any shipped thing is postable. The Ship pattern leads with what changed and why it matters to the user.

The reasoning behind a non-obvious technical or product choice. Why you chose Supabase over PlanetScale. Why you removed a feature. Why you rewrote the auth flow. The Decision pattern is for choices that had real trade-offs.

Removing something is underrated content. Code deleted, features cut, approaches abandoned. The Deletion pattern is for commits where the diff is mostly negative lines. What you removed and why.

Recovery from a broken state, a failed experiment, or a wrong direction. The Comeback pattern is for commits that follow a period of struggle or inactivity. It documents resilience.

A version, a launch, a number crossed. Real markers, not manufactured celebration. The Milestone pattern is for commits tagged to a release or a significant project threshold.

Short-form video hook

5 lines. Opens with a hook sentence, followed by three tight support lines, closes with a CTA or reframe. For YouTube Shorts, Reels, TikTok.

Long-form video hook

2–3 sentence setup that builds tension, followed by the payoff statement. For YouTube long-form introductions.

X Thread

Numbered tweets. Tweet 1 is the hook. Tweets 2–5 are standalone insights. Final tweet is a CTA or summary. Each tweet works alone.

LinkedIn post

Hook line (never "I am excited to share"). Three to four short paragraphs, one topic each. Closes with a question or CTA.

Marketing post

Problem (one sentence). Solution (one to two sentences). Proof or specificity (one sentence). CTA (one sentence). For product pages and announcements.

Filtering:

Filter by pattern (Struggle, Ship, Decision, Deletion, Comeback, Milestone), by format, or show saved pieces only.

Expanding a piece:

Click any row to expand it inline. The full piece, why it works, and a Copy button appear below the row. Click again to collapse.

Save:

Mark a piece as saved to keep it at the top of your list. Saved pieces do not expire.

Dismiss:

Remove a piece you will not use. Dismissed pieces are hidden but not permanently deleted.