Bubblegunn
UserYour agent ships code. product-engineer makes it ship outcomes. Four agent skills plus a zero-dependency check for the For-the-customer block in commits and PRs.
Categories
Indexed Skills (5)
product-engineer
Use when building, changing, or describing software for other people. Makes the agent restate work as a customer outcome, write a plain-language "For the customer" block in every commit and PR, refuse to call unobserved work done, name what it deliberately did not build, and never print a number it did not count.
release-notes
Use when writing release notes, a changelog entry, a status update or a "what's new" message for people who do not read code. Makes the agent lead with what the reader can do now, keep one line per change, explain every term, count every number, and list what is not in this release.
customer-block
Use when writing a commit message or a pull request description for software other people use. Ends every message with a plain-language "For the customer" block, what changed, why it matters, and an automation effect only when a manual step really disappeared.
done-means-observed
Use when reporting that a piece of software work is finished. Makes the agent report what it watched happen in logs, data or on a real device, and say exactly what it could not check, instead of calling work done because tests pass.
ai-slop-linter
Before finishing any prose you wrote (commit message, PR description, README, docs, article), run ai-slop-linter on it and fix every finding. Also use when the user asks whether text "sounds like AI", asks to humanize text, or asks to remove em dashes.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.