vøiddo devlog
ship every week. write about it.

Your commits deserve a blog post.

Paste your GitHub URL or git log. We pull your last 7 days of commits and generate a blog post, tweet thread, and LinkedIn post in under 30 seconds.

// your git log
a3f9c1b fix: mobile nav collapse on scroll
7e2d884 feat: add Stripe webhook retry logic
c5891ba perf: lazy-load product images
f1a0372 fix: checkout button disabled state
2bd6c03 chore: bump deps, remove lodash
// generated devlog
BLOG POST
Week 14: Shipping the Boring Stuff (That Actually Mattered)
This week was less "feature drop" and more the invisible work that makes everything else hold together. Here's what shipped — and why it was worth it...
GitHub URL
Paste commits
Pro (unlimited)
payment confirmed
Your Pro license is on its way.
Check the inbox you used at checkout for a license key from devlog@voiddo.com, then paste it into the Pro form below to generate unlimited devlogs. If it does not arrive within 2 minutes, email support@voiddo.com and we will resend it.
1 free preview per day. Paid results are emailed and also viewable at your result link.
Free preview
3 grounded bullets from your commit history
Paste a public GitHub repo or your last 7 days of commits. We keep the preview short, factual, and grounded in the input.
    the process

    How it works

    Three steps. No onboarding, no accounts, no explaining your project to an AI.

    $
    01 / input

    Paste a URL or git log

    Public repos work without any auth and default to your last 7 days of commits. Or run git log --since=\"7 days ago\" --oneline and paste the output.

    ~
    02 / generate

    We turn commits into narrative

    Our AI model reads what you built and writes a 400-word blog post, 5-tweet thread, and LinkedIn post — all in one shot.

    >
    03 / receive

    Content lands in your email

    Three pieces ready to post. Takes under 40 seconds to generate after payment confirms.

    what you get

    Real output, not a template

    Generated from actual commit messages. You can inspect a grounded public sample before paying.

    message-next-step · grounded sample
    public sample
    Blog post
    Tweet thread
    LinkedIn
    Refining the `message-next-step` CLI

    This past week, focus for `message-next-step` has been on foundational improvements. Several adjustments have been made to the project's build and testing infrastructure.

    A key piece of work involved addressing an issue with the binary executable bit. This was done to ensure the CLI can be installed globally and run correctly. Resolving this ensures that users who install `message-next-step` will find it ready to go.

    To support these efforts, a new test file, `test.js`, has been introduced. This addition signifies a commitment to verifying the project's behavior.

    Additionally, `src/index.js` has been added, which serves as the main entry point for the project's logic, and `site/styles.css`, suggesting early work on a potential website or documentation interface.

    Overall, this week's work has been about solidifying the project's core mechanics and setting up better practices for testing and development.

    1 / 5
    Updates for `message-next-step` this week, focusing on core CLI functionality. 🧵
    2 / 5
    We've addressed an issue with the bin executable bit, ensuring the CLI installs and runs correctly when installed globally.
    3 / 5
    To bolster reliability, we've added a `test.js` file. This helps verify behavior.
    4 / 5
    Also added `src/index.js` (the main entry point) and `site/styles.css`, laying groundwork for future development.
    5 / 5
    These foundational improvements and fixes are all part of building a more robust `message-next-step`.
    This week, focus has been on refining the core of `message-next-step`.

    Key updates include fixing the binary executable bit for the CLI, ensuring a smoother global installation and execution experience for users.

    Development process has been strengthened by adding a `test.js` file, which will be instrumental in verifying functionality.

    Alongside this, `src/index.js` has been introduced as the entry point for the project's logic, and `site/styles.css`, hinting at early work on a potential website or documentation.

    These foundational improvements are crucial for building a reliable tool.

    Want proof before paying? Open the full grounded sample result page we keep public. It is generated from a real commit set, not written by hand for the landing.
    See full sample result
    pricing

    One generation or unlimited

    No subscriptions required. Pay per generation, or go unlimited if you write every week.

    One-time
    $9 / generation
    One blog post, one tweet thread, one LinkedIn post. Emailed to you. Viewable at your result link for 30 days.
    • -> Blog post (300–400 words)
    • -> 5-tweet thread with hook
    • -> LinkedIn post (150–200 words)
    • -> Public GitHub repos supported
    • -> Or paste your git log
    • -> No account needed
    One-time payment via Paddle
    Pro — Unlimited
    $19 / month
    Generate as many devlogs as you want. License key emailed immediately — no checkout friction every time.
    • -> Everything in one-time
    • -> Unlimited generations
    • -> License key — no checkout per use
    • -> Cancel anytime
    License key emailed immediately
    questions

    FAQ

    Does it work on private repos?+
    Public GitHub repos work directly via the GitHub API and use the last 7 days of commits by default. For private repos, run git log --since=\"7 days ago\" --oneline and paste the output. No OAuth needed.
    How long does generation take?+
    Usually 20–40 seconds after payment confirms. You'll get an email with all three pieces of content, plus a link to view anytime.
    Can I edit the output?+
    Yes. The output is plain text — copy it wherever you write. It's meant to be a solid first draft, not something you're afraid to touch.
    What if the generation fails?+
    Email support@voiddo.com and we'll regenerate or refund. We track failures and fix root causes.
    Is my code sent anywhere?+
    We only read commit messages — not source code. Commit messages are sent to our AI provider for generation, and the output is grounded in those commit messages plus the repo context you provide. Don't paste secrets or private tokens into commit text.
    How do I cancel the Pro subscription?+
    Email support@voiddo.com with your email address. We cancel immediately. You keep access until the period ends.