Skip to content

Your way of working

It runs on your skills, your rules and your tools.

Keep your team's skills and agent briefs in a repository and CoderHelm reads the ones that fit the work. Connect the MCP servers you use and it pulls context from them while it plans and builds.

Get startedRead as Markdown
app.coderhelm.com/skills
example/team-skillssynced after last merge
  • skills/release-checklist/SKILL.mdskill · read 14 times this week
  • skills/graphql-conventions/SKILL.mdskill · read 31 times this week
  • agents/reviewer.mdagent brief · read 22 times this week
  • commands/add-migration.mdcommand · read 5 times this week

Text only. Nothing from this repository is ever run.

A connected skills repository: each skill and agent brief, its switch, and how often the agents read it.

Skills kept in a repository

  • Skills from skills/<name>/SKILL.md or .claude/skills/<name>/SKILL.md, with the text files next to them
  • Agent briefs from agents/<name>.md and command steps from commands/<name>.md
  • Read from the default branch only, so only merged, reviewed text is used, and synced after every merge
  • Text only: nothing from a skills repository is ever run, and every guard stays in place
  • Each item has a switch, and you can see how often each agent read it

Your rules

CoderHelm reads AGENTS.md, CLAUDE.md, copilot instructions and .cursorrules from each repository. Admins add guardrails, custom instructions and a team voice for pull request descriptions.

MCP servers

Connect any of 17 MCP servers and CoderHelm can use them while it plans and implements: Figma, Sentry, Linear, Notion, Vercel, Stripe, PostHog, GitLab, Neon, Turso, Snyk, LaunchDarkly, MongoDB Atlas, Grafana, Redis, Upstash and Sanity. Credentials are stored encrypted with AWS KMS.

Memory you can see

CoderHelm remembers what it learns on each repository, kept per team and per repository. Each agent has a profile showing what it knows and where it learned it, and you can pin, edit, forget or teach it something new.

Related

  • Tickets to PRs

    Assign a GitHub issue or Jira ticket to CoderHelm and it plans the change, writes it on its own branch, runs your build and tests, reviews its own work and opens a pull request.

  • Data sources

    CoderHelm checks your GraphQL API, CloudWatch Logs, PostgreSQL and Redshift while it plans, writes and reviews, with every lookup read only, enforced in code and recorded.

  • Code review

    Add a label to any GitHub pull request and CoderHelm reviews it with the context of the whole repository, comments on exact lines with suggested fixes, rates risk and reviews again on every push.

Put CoderHelm on your next ticket.

CoderHelm is in open beta. Sign up and bring your own Anthropic API key.

Get startedSelf-host itTalk to us