Use Buron in your AI editor

The most common way teams use the Buron CLI is from inside their AI editor. When you link a project, we drop a set of slash commands into Claude Code, Cursor, Codex, or whatever editor you use. From there, your editor's agent has a direct line to your Buron team. It can pull context from your team's docs, capture work in progress, and take Buron actions without leaving the conversation.

You don't have to invoke the CLI yourself. Your editor's agent does, on your behalf.

Where the skills live

We auto-detect which folder your editor reads from and install the skills there.

• .cursor/skills/ for Cursor
• .claude/skills/ for Claude Code
• .github/skills/ for GitHub Copilot
• .codex/skills/ for Codex
• .agents/skills/ for everything else

You don't have to set anything up. Running buron link is enough.

Snapshot a code change with /launch

/launch is a good first skill to try. Type it in your editor while you're working on a change. The agent captures everything around that change, like the git diff, the PR description and review comments, and screenshots you've shared in the conversation. It saves all of this as a structured snapshot in Buron.

The result is that the next person who asks Buron about that change has the full story without you having to write it up. It's especially handy on features that span multiple PRs or that touch parts of the product your marketing team will need to talk about.

Set up Google Ads conversion tracking with /setup-google-ads-tracking

If you're wiring up conversion tracking in code, like on a new pricing page or signup flow, /setup-google-ads-tracking walks the agent through it. You describe the event you're trying to track, and the skill produces the tracking spec, the code change, and a doc that goes into Buron.

To learn more about this skill, check out Set up your conversion tracking.

Keep your skills up to date

We add new skills and revise existing ones as Buron evolves. To pull in the latest versions, run:

buron skills update

It's a good idea to run this after major Buron releases, or whenever a teammate mentions a new command.

Skills are scoped to the project you've linked. To work across multiple repos, run buron link in each one. Every project gets its own skill set tied to the right team.

Next steps

To keep Buron in sync with what your codebase ships, check out Run Buron from CI.