Model or dataset
rokpiy/auto-commenter avatar
rokpiy/auto-commenter

auto-commenter: a Claude skill for posting Reddit comments in your own writing style

A Claude skill that automatically posts personalized, authentic comments in your target communities.

586 stars115 forksUnknownMIT

At a glance

What is it?
auto-commenter packages a Reddit commenting workflow as a Claude skill driven by Playwright MCP. It is a prompt-and-resource system rather than a commenting engine, and its quality depends entirely on the personalization files you supply.
Who is it for?
Adopt auto-commenter only if you already comment on Reddit by hand and want the drafting and logging steps automated under your own style guide. Skip it if you need unattended posting at scale, because the README itself tells you not to automate 100% of activity and the skill has no built-in scheduler.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.

DEEP OPEN-SOURCE ANALYSIS

The problem: generic bot comments get noticed and removed

Most comment automation produces text that reads like automation. The README frames the project against that failure mode directly, describing typical bots as producing obvious automated comments. auto-commenter's answer is not a better generator but a style-transfer layer: it asks you to collect 8 to 10 comments you have already written, across various topics, lengths and tones, and have an LLM turn them into a personalization guide. That guide becomes the voice the skill writes in.

The intended user is a solo operator or small marketing team doing community-led growth on Reddit, where the README says support currently exists. The repository also lists product.md as an optional resource for people promoting a product, and leads/reddit.md as the place where potential customers get recorded. So the design assumes a commercial motive sitting behind the comments, which is worth stating plainly rather than treating as incidental. If you have no product and no target subreddits, the skill has nothing to personalize against.

How the skill is structured: markdown resources, not code

The repository layout is the clearest description of the mechanism. Under .claude/skills/reddit-commenter/ there are two workflow files, SKILL.md for a single comment and BATCH.md for batch execution, plus a resources/ directory holding personalization_reddit.md, subreddits.md and product.md. Two output directories sit outside the skill: tracking/reddit/ for daily activity logs and leads/reddit.md for discovered prospects.

That means the behaviour of the tool lives in prose instructions and reference documents that Claude reads at run time. There is no scoring model, no classifier, no ranking service. The README says the skill analyzes posts deeply to understand context and intent rather than matching keywords, and that generated comments pass a 16-point quality checklist, but the checklist itself is not reproduced in the README. Whether it is a list in SKILL.md or a section of the personalization file cannot be confirmed from the supplied material. The same applies to how posts are selected: the README says the skill analyzes posts, and that the browser side runs through Playwright MCP, so the reading and posting steps are browser actions, but the exact selection procedure is not documented here.

The npm install in the quick start is the only code-level dependency mentioned. Everything else is configuration by document.

Getting it running: clone, install, then write three markdown files

The quick start is four steps. Clone and install:

git clone https://github.com/rokpiy/auto-commenter.git cd auto-commenter npm install

Then build the personalization file. The README's instruction is to collect 8 to 10 of your own comments, ask an LLM to analyze them and produce a personalization guide, and paste the result into .claude/skills/reddit-commenter/resources/personalization_reddit.md. Next, target communities: ask an LLM to analyze your target subreddits and paste their rules, tone and good topics into .claude/skills/reddit-commenter/resources/subreddits.md. If you are promoting something, add details to .claude/skills/reddit-commenter/resources/product.md.

Running it is conversational rather than command-line. The README gives three invocations: "Write one comment on r/YourSubreddit" for a single comment, "Fill today's quota" for batch mode, and "Show today's Reddit activity" to read the tracking file. Batch mode is documented as defaulting to 3 comments per subreddit with 5 to 15 minute intervals, and the tracking file is named by date, for example tracking/reddit/2026-01-30.md. The README also points to SETUP.md for the full guide and QUICK_REFERENCE.md for commands and tips, neither of which is included in the material supplied here.

Batch mode, quotas and the tracking file

The batch workflow is where the project's operational assumptions show. The README describes a default of 3 comments per subreddit and cites an example of 24 comments across 8 subreddits to fill a daily quota. Intervals of 5 to 15 minutes are described as spacing between posts, which reads as an attempt to look less mechanical than a burst of comments.

Tracking is file-based. Each day gets a markdown log under tracking/reddit/ with comment links and metrics, and leads/reddit.md accumulates prospects the skill judged to be interested in your product. This is a lightweight design with a real consequence: the log is only as accurate as the model's willingness to write to it, and nothing in the described architecture reconciles a claimed post against the actual Reddit thread. If you need an auditable record of what was published, you are relying on the same agent that published it to keep the books.

The quota numbers are defaults stated in the README, not measured throughput. How long a batch actually takes depends on generation time and the interval chosen, and no timing figures are given.

The responsible-use section is also the honest limitation

The README carries a warning block stating that the tool enhances genuine engagement rather than replacing it, and lists four don'ts: don't spam or deceive communities, don't claim false experiences, don't ignore negative feedback, don't automate 100% of activity. It also tells users to mix in manual comments.

Read literally, that is a constraint on the product's own value proposition. A tool whose selling point is filling daily quotas is simultaneously telling you not to let it do all the work. Reddit's own moderation is the reason: subreddits enforce their own rules, and the README's remedy is that you paste those rules into subreddits.md so the model can respect them. That is a soft control. It depends on the model reading the file, understanding the rule, and choosing to comply on every generation. There is no enforcement layer described.

The second limitation is scope. Reddit is the only supported platform. The multi-platform path is manual: copy .claude/skills/reddit-commenter/ to a new platform directory, write a new personalization file, and update SKILL.md and BATCH.md for that platform's APIs or browser automation. The README lists Twitter, LinkedIn and Discord templates as coming soon, which means today you would be authoring the browser automation yourself. And because posting runs through Playwright MCP against a logged-in session, a login prompt, a CAPTCHA or a layout change on the site breaks the run in a way that no amount of prompt tuning fixes.

What a plain Playwright script does differently

The obvious alternative is a direct Playwright script that logs in, navigates to a subreddit, and submits comment text you supply. The difference is where the intelligence sits. A script has no opinion about what to say; you write every comment, and the script handles the mechanics of typing and submitting. auto-commenter inverts that: the model decides what to say, and Playwright MCP is only the transport layer for reading posts and posting replies.

That inversion is the whole product, and it is also the whole risk. With a script, the failure mode is a broken selector. With auto-commenter, the failure mode can be a comment that is well-formed, on-topic, in your voice, and still something you would not have said. The 16-point checklist is meant to catch that, but a checklist applied by the same model that wrote the text is a weaker guarantee than a human reading it before it goes out. If your goal is volume with a human approving each comment, a script plus a draft queue gives you the same leverage with a harder gate. If your goal is genuinely hands-off commenting, auto-commenter is the only one of the two that attempts it, and the README's own guidance argues against using it that way.

Licence and what maintenance actually costs

The project is MIT licensed, which permits commercial use, modification and redistribution provided the copyright notice and permission notice are retained. If you fork it to build a LinkedIn or Discord variant, you keep the MIT notice in the copy. That is a statement about the licence text, not legal advice; if you are embedding this in a product, have counsel read the actual LICENSE file rather than a badge.

Maintenance cost is dominated by the resources, not the code. personalization_reddit.md and subreddits.md are living documents: your voice drifts, subreddit rules change, and the README's own workflow assumes you regenerate the personalization guide from fresh samples. Every platform you add is a new directory plus a rewritten SKILL.md and BATCH.md. The npm side is thin, so dependency churn is unlikely to be the problem. The repository shows no releases retrieved, so there is no versioned upgrade path to follow; you would be tracking the main branch and reviewing changes yourself. Last push was 2026-03-15, which tells you the project was active as of that date and nothing more.

Editorial conclusion

Adopt auto-commenter only if you already comment on Reddit by hand and want the drafting and logging steps automated under your own style guide. Skip it if you need unattended posting at scale, because the README itself tells you not to automate 100% of activity and the skill has no built-in scheduler. Before running anything, verify that Playwright MCP is installed and connected to a logged-in browser session, and check that the subreddit rules you paste into subreddits.md actually permit promotional comments.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. rokpiy/auto-commenter on GitHub
Community notes

Community notes