Fowel automatically reviews documentation in every GitHub pull request – catching inaccuracies, missing context, outdated code samples, and structural gaps before they reach production. Install in 30 seconds and scale across unlimited repositories.
Last week I got hit by a client with "sorry we took all the docs work your team did over the last 3 months which was great, fed it to Claude Code and we're good going forward". $5k+ MRR up in smoke.
I think that's when I might have finally gotten past the denial stage, that AI is coming for my company, Hackmamba, a technical content agency, even though we're focused on authenticity and technical creativity.
As an engineer and technical writer (now double-screwed I guess) I'm a big purporter that AI is like electricity, making things better, but the last 2 weeks have been, shocking (pun intended). Maybe I'd just been slow, doing too much talking and less doing.
So what did I do after J hit me with the contract cancellation line, I started looking for ways to do more with AI without crossing the blurry line that is generating slop. As a former PM, the first culprits of my evaluation were anything we spent more than 10 hours per month doing.
Technical reviews came up first. We work in teams shipping fast and need to get docs ready for developers and agents. Documentation is the ground truth before MCPs etc take over. So we spend a good amount of time reviewing docs PRs sent in by technical writers for accuracy, tone, shit code, typos, consistency with the overall style, persona match, clarity for sales and marketing usage etc.
So I did the next logical thing a software engineer (bless that job title) would do; I made a system prompt with everything we know and documented internally, plus everything I know about docs, individual frameworks, patterns etc. Then I built Fowel.ai (should sound like vowel, not foul) with it to handle deep GitHub PR reviews on documentation that was both written by a human or AI generated.
Frankly, I don't care at this point. If the end goal is to ship great docs for humans and agents, why care deeply about who wrote it. AI agents don't care, and I've worked with writers worse than GPT 5.4. We likely won't need documentation in the future too when we fix agent<>agent comms 🫠
Maybe I'm cooked for making such mental shift towards building the guardrails and quality enforcements. Time will tell.
We've seen a huge reduction in time to get PRs into production by about 80%, which I love. Do try Fowel if you're looking at the speed of getting great docs content out, and I appreciate any feedback shared. It's free to use. Thanks in advance and let me know if this is shit too.
fmerian,
Last week I got hit by a client with "sorry we took all the docs work your team did over the last 3 months which was great, fed it to Claude Code and we're good going forward". $5k+ MRR up in smoke.
I think that's when I might have finally gotten past the denial stage, that AI is coming for my company, Hackmamba, a technical content agency, even though we're focused on authenticity and technical creativity.
As an engineer and technical writer (now double-screwed I guess) I'm a big purporter that AI is like electricity, making things better, but the last 2 weeks have been, shocking (pun intended). Maybe I'd just been slow, doing too much talking and less doing.
So what did I do after J hit me with the contract cancellation line, I started looking for ways to do more with AI without crossing the blurry line that is generating slop. As a former PM, the first culprits of my evaluation were anything we spent more than 10 hours per month doing.
Technical reviews came up first. We work in teams shipping fast and need to get docs ready for developers and agents. Documentation is the ground truth before MCPs etc take over. So we spend a good amount of time reviewing docs PRs sent in by technical writers for accuracy, tone, shit code, typos, consistency with the overall style, persona match, clarity for sales and marketing usage etc.
So I did the next logical thing a software engineer (bless that job title) would do; I made a system prompt with everything we know and documented internally, plus everything I know about docs, individual frameworks, patterns etc. Then I built Fowel.ai (should sound like vowel, not foul) with it to handle deep GitHub PR reviews on documentation that was both written by a human or AI generated.
Frankly, I don't care at this point. If the end goal is to ship great docs for humans and agents, why care deeply about who wrote it. AI agents don't care, and I've worked with writers worse than GPT 5.4. We likely won't need documentation in the future too when we fix agent<>agent comms 🫠
Maybe I'm cooked for making such mental shift towards building the guardrails and quality enforcements. Time will tell.
We've seen a huge reduction in time to get PRs into production by about 80%, which I love. Do try Fowel if you're looking at the speed of getting great docs content out, and I appreciate any feedback shared. It's free to use.
Thanks in advance and let me know if this is shit too.
I don't mind brutal feedback.
William.