
Auto Build In Public
https://github.com/juliusbrussee/auto-build-in-public- Category
- Social
- Rank
- No. 2221Tools index
Previous survey · No. 2184 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- JuliusBrussee
- GitHub
- 4 stars
- Date
About
Automatically generate post-ready build-in-public drafts from your git history, optionally triggered on merged PRs.
What it does
Auto Build In Public turns repository changes into editable social content. It reads bounded pull request or local Git context, adds product and voice configuration, then asks an OpenAI model for X and LinkedIn drafts. Each event gets three editorial angles. The resulting Markdown stays in the repository for human editing and manual posting.
Why it's ranked here
The tool has a useful, inspectable workflow: bounded context goes through budget checks, redaction, output validation, and versioned Markdown writeback. It also supports local use, GitHub automation, diagnostics, personas, scheduling, and MCP clients. The main concern is maturity. The roadmap still marks the safety and privacy gate as unfinished, and one error path restores original context after redacted context cannot be parsed.
What's good
It avoids sending raw diffs during pull request collection. Instead, it gathers metadata, changed filenames, addition and deletion counts, and a truncated pull request body. Configuration covers personas, platform style, detail level, denylist patterns, custom secret patterns, and output blocking. Drafts remain ordinary Markdown with source and safety metadata, so teams can inspect, edit, and version them before publishing.
Tradeoffs
Local generation requires Node.js 20 or newer, Git, and an OpenAI API key. The documented CLI installation still builds and links directly from the repository, rather than showing a normal package installation. Automated writeback needs repository content write permission. Posting remains a copy-and-paste step. Most importantly, redacted-context parsing failure can fall back to the original context, while the roadmap describes the safety gate as unfinished.
How to use it well
It best fits solo founders, open source maintainers, and developer-tool teams already treating pull requests and commits as a shipping log. Run it after meaningful Git ranges or from a reviewed GitHub workflow, keep redaction enabled, and inspect every draft before posting. It handles draft creation and repository writeback. It does not publish to social networks or replace editorial judgment about confidential details and audience relevance.
Technical notes+
The TypeScript CLI in action/src/cli.ts supports interactive operation, diagnostics, GitHub connection, repository installation and management, scheduling, immediate generation, and local range-based generation. action/src/index.ts implements the GitHub Action, collects configuration and bounded GitHub context, applies budget enforcement and redaction, calls generateAllDrafts, writes Markdown, and exposes Action outputs. action/src/context/pr.ts truncates pull request bodies and caps changed-file records at 100 without fetching raw diffs. action/src/agent/state.ts stores local repository state and GitHub credentials under the user home directory with mode 0600. mcp-server/src/server.ts exposes four tools and three resources over stdio. action/bin/persona.ts provides an interactive persona creation, resume, edit, list, and export flow.
Observed
- License
- MIT License
- Primary language
- TypeScript, with JavaScript entrypoint and build-helper files also shown
- Runtime
- Node.js 20 or newer
- Install surface
- Repository-built CLI using npm build and npm link, plus a bundled GitHub Action
- Interfaces
- Interactive and command-based CLI, GitHub Action, and MCP server over stdio
- Generated formats
- Markdown drafts for X and LinkedIn with frontmatter metadata
- Model requirement
- Local LLM draft generation requires an OpenAI API key
- Automation scope
- Manual runs, pull request workflows, and scheduled workflows are documented
Read from README.md, action/src/cli.ts, action/src/index.ts, action/src/types.ts, action/bin/persona.js, action/bin/persona.ts, mcp-server/src/index.ts, mcp-server/src/server.ts, action/bin/addShebang.js, action/src/agent/home.ts, action/src/context/pr.ts, action/src/agent/repos.ts, action/src/agent/state.ts, action/src/agent/doctor.ts, action/src/agent/format.ts.
What it can do
Generate build-in-public post drafts from git commit history
Git repository history → Post-ready build-in-public draft content
Automatically trigger post generation on merged pull requests
Merged pull request events → Build-in-public post drafts
Parse git commit messages into readable updates
Git commit messages and metadata → Formatted progress updates
Transform code changes into user-friendly narratives
Git diff and commit data → Human-readable development progress stories
Schedule automated post creation based on repository activity
Repository webhook events → Scheduled build-in-public content
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.