Crux compared / CommitLore
CommitLore vs Crux: two ways to turn commits into posts
Both products start from your commits. CommitLore waits for a command in a commit message and reads the code change; Crux drafts from every push, merged pull request and release on the repos you pick, without opening a file, and then follows each postβs numbers.
Updated
CommitLore turns GitHub commits into draft posts for social networks and blogs. You add a CommitLore command to a commit message, it analyses the diff, the changed files and their context, and the draft waits in a dashboard for your approval, after which it can be published to your connected accounts in one click. Crux (cruxpost.com) needs no command and never reads code: it drafts from commit messages, pull request and release text and the names of changed files, can take a note from your coding agent through its plugin, and after you post it measures each post at 1 hour, 24 hours and 7 days against your usual post, so it can tell which kinds of post work for you.
What CommitLore is
CommitLore describes itself as a way to turn commits into content. You opt a commit in by adding a CommitLore command to its message; the tool then reads the diff, the files that changed and the surrounding context, and writes a draft. Drafts collect in a dashboard and wait for your approval, and approved drafts go out to all your connected platforms with a single click. A weekly digest arrives every Sunday.
You pick a tone, such as professional, casual or technical, for the AI to write in. An engagement dashboard tracks likes and comments on what was posted. The connectable outlets are π, LinkedIn and a blog, with Dev.to and WordPress added on the Pro plan.
Crux and CommitLore, side by side
| Feature | Crux | CommitLore |
|---|---|---|
| Drafts posts from your GitHub work | Yes. Each push to a watched repoβs default branch, merged pull request and published release becomes three drafts in your voice, written by a free model through OpenRouter. Work is grouped until it has been quiet for 3 minutes; a release is drafted at once. | Yes, for commits whose message carries a CommitLore command. |
| What it reads from your repos | Commit messages, pull request and release titles and text, the names of the files a commit changed, and repo names, through a read-only GitHub App on the repos you choose. Never a file or a diff. | The diff, the changed files and their context. |
| Posts to π for you | Only what you schedule, on Autopilot. Sign-in is read-only (tweet.read, users.read, offline.access). Drafts wait in your Inbox: Post on π copies one and opens π with it, for you to post. | Yes, after you approve a draft: one click publishes to your connected platforms. |
| Learns from how your posts do | Yes. Each postβs numbers at 1 hour, 24 hours and 7 days, against your usual post. Learnings show which kinds of post (launch, feature, fix, improvement, milestone or other), hooks, formats and topics do better or worse for you, and drafts are written with them. | An engagement dashboard shows likes and comments. Its site does not say the results change later drafts. |
| Tests patterns against chance | Yes. A group of at least 5 posts is reported only when it falls outside 500 random draws of your own posts. | Not stated on their site |
| Coding agents and API | The Crux plugin for Claude Code and Codex sends your coding agentβs note on what changed, why and for whom, with a token you create in Settings. | Not stated on their site |
| Networks | π only. | π, LinkedIn and a blog; Dev.to and WordPress on Pro. |
| Price and trial | Pro is $19 a month or $180 a year ($15 a month), and the launch deal is Pro for life for $49 once, for the first 100 buyers. Every account starts with a 7-day free trial of Pro that needs no card. When it ends without a paid plan, the account is read-only: you can still see, download or delete your data, and choose a plan. Cancel anytime. | Starter: 12 USD a month (3 repositories, 5 drafts a day, π and LinkedIn, a free trial of 14 days). Pro: 29 USD a month (10 repositories, 15 drafts a day, all platforms). Team: 49 USD a month, marked coming soon. Enterprise: custom. No card required. |
CommitLoreβs column was checked against its own site on : commitlore.com. βNot statedβ means we found nothing about it there that day, not that it cannot exist. Prices and plans change: check their site for todayβs.
The difference that matters
The biggest split is the code. CommitLore reads your diff to understand a change. Crux deliberately never fetches a file or a diff: it works from what you already wrote about the change, in commit messages, pull request descriptions and release notes, plus the names of the files touched and, if you use the plugin, a short note from your coding agent. If your repo is private, that is a real difference in what leaves it.
The trigger differs as well. With CommitLore you decide in the moment, commit by commit, by typing a command. Crux watches the default branch of the repos you choose, waits until a burst of work has gone quiet, and drafts once per batch, so a busy afternoon becomes one set of drafts instead of twelve.
Moving from CommitLore, or using both
Nothing has to be migrated. Whatever CommitLore published to π sits on your timeline like any other post, and Crux reads your history from your π archive or a read-only import, so those posts become part of the baseline every new post is measured against.
Running both on one repo would give you two sets of drafts for the same work. If you try Crux alongside, stop adding the CommitLore command to your messages for that repo, and compare after a couple of weeks which drafts you actually posted.
Which one to pick
Pick CommitLore instead ifβ¦
- You want drafts that draw on the code change itself, not only on what you wrote about it.
- You want to choose, commit by commit, which ones become posts.
- You publish to LinkedIn, a blog, Dev.to or WordPress as well as π.
Pick Crux ifβ¦
- You would rather no tool read your code, private or not.
- You want drafts to arrive on their own after a push, a merge or a release.
- You want each post measured against your usual one and patterns tested against chance.
- You use Claude Code or Codex and want the agent to explain the change for the draft.
Other comparisons
- Crux vs OpenTweet: OpenTweet schedules and posts to π, with connectors and an agent API. Crux drafts from your GitHub work and learns what works for your account.
- Crux vs Commit To X: Commit To X writes a quick AI post per commit for you to copy. Crux batches work, writes in your voice and learns from results.
- Crux vs buildinpublic.now: Its site answered with a paused deployment when we checked. Crux drafts from your GitHub work and learns from results.
- Crux vs PubliclyBuild: Its domain did not resolve when we checked. Crux drafts from your GitHub work and measures every post.
- Crux compared with X growth tools