An Indie Hackers builder runs event-driven agents: when backend changes land, webhooks update TypeScript/Python SDKs, run tests, draft changelogs/PRs, and only deploy if checks pass—plus a morning schedule that drafts Agent Store listings for review.
A Reddit X20 user runs nine scheduled ChatGPT agents across a repo—PR bugs, perf sweeps, docs clarity, unfinished features—each posting to its own GitHub issue as a message board, with human approval before merges.
The example distinguishes waiting reviews, requested re-reviews, and approved changes and prepares reminders containing the work's size and blocking context.
The example narrows a funnel change by cohort and authentication path, then correlates analytics, tickets, and deployment history to investigate likely causes.
The skill investigates a target company's GitHub contributions, engineering writing, and conference activity, then cross-checks professional identities before proposing outreach targets.
Zachary Proser queues 5–7 maintenance, bugfix, and small-feature tasks each morning; Cursor background agents clone sandboxes, branch, and open draft PRs with ~70–80% one-shot success.
@GitHub in Slack and Microsoft Teams can now answer across multiple repositories in one thread—open PRs, weekly merges, cross-frontend/backend investigations—plus use shared Slack thread context without copy-paste.
Anthropic’s Claude Code team documents a layered review stack—pre-PR verify, AI review + security block, risk-tiered human approvals, merge queue/flags, and fast rollback—so most agent PRs merge with ≤1 human while revert rate fell >40% as volume doubled.
Merlin dispatches team asks from Slack/Linear/GitHub to Claude Code or Codex already signed in on teammates’ machines—reuse local repos, MCP servers, and skills with no extra model API bill; results return in the same thread, with shared skills, schedules, and workspace memory.
An Indie Hackers walkthrough connects a Jotform request, n8n planning and content generation, a GitHub branch, a Vercel preview, an approval step, and post-change monitoring.
Zack Proser's review describes assigning repository-and-branch-specific maintenance jobs to Cursor Agents, following up in each task's own context, and opening the changes directly in the editor for hands-on refinement.
A VLM Run workflow parses emailed resumes, analyzes linked GitHub activity, and records a technical candidate profile with notifications for the recruiting team.