cobrew

CoBrew

Install standardized AI workflow skills for coding agents.

Use the CoBrew plugin for the best Codex and Claude Code experience. For other agents or environments without plugin support, install the skills directly with the Vercel skills CLI.

---

Languages: English | Tiếng Việt

---

What it does

CoBrew ships the same first-party workflow skills through two supported paths:

1. Plugin bundles for Codex and Claude Code expose self-contained workflow skills directly through each agent's plugin system.
2. Direct skills CLI install uses the Vercel skills CLI to install the same skills into other supported agents.

Installation

Codex plugin (recommended for Codex)

Install the CoBrew plugin marketplace directly from GitHub:

codex plugin marketplace add buiducnhat/cobrew

Claude Code plugin (recommended for Claude Code)

Install the CoBrew plugin marketplace directly from GitHub:

claude plugin marketplace add buiducnhat/cobrew

Inside an interactive Claude Code session, use the slash command form:

/plugin marketplace add buiducnhat/cobrew

Other agents

For agents outside the plugin path, install the CoBrew skills directly:

npx skills add buiducnhat/cobrew

Plugin bundle maintenance

This repository treats the root skills/ directory and plugins/cobrew/.codex-plugin/plugin.json as the authoring metadata source for plugin bundles.

bun run sync:plugin generates a self-contained plugin bundle at plugins/cobrew/, including both Codex (.codex-plugin/plugin.json) and Claude Code (.claude-plugin/plugin.json) manifests.

It also rewrites the Codex marketplace at .agents/plugins/marketplace.json and the Claude Code marketplace at .claude-plugin/marketplace.json so both point at ./plugins/cobrew.

Each workflow skill includes its own project context-loading guidance and uses docs/SUMMARY.md as the entry point when present.

Repository workflow skills

This repository currently defines ten first-party workflow skills and also pins additional upstream skills in skills-lock.json:

Skill	Description
ask	Ask clarifying questions to gather requirements and context
fix	Diagnose and resolve bugs with root-cause analysis and verification
review	Review uncommitted changes with codebase context and severity levels
brainstorm	Explore ideas and break down complex problems before planning
docs	Create or refresh project documentation based on the current repo
execute-plan	Execute written plans systematically with checkpoints
git-commit	Create conventional commit messages from staged or unstaged changes
quick-implement	Rapid implementation for small, well-scoped changes
visualize	Create source-adjacent HTML visualizations for docs, markdown, plans, and context using fixed templates and Mermaid
write-plan	Create detailed implementation plans with phases and tasks

Recommended workflow sequences

---

Init documentations

/docs

Complex or ambiguous tasks

brainstorm → write-plan → execute-plan

Use when requirements are unclear or multiple approaches are possible.

# Step 1 — explore and define the design
/brainstorm add dark mode support

# Agent clarifies requirements, proposes approaches, writes:
#   docs/brainstorms/260306-1430-dark-mode/SUMMARY.md
# Then prompts: "Proceed to write-plan?"

# Step 2 — create a phased implementation plan
/write-plan

# Agent reads the brainstorm, writes:
#   docs/plans/260306-1445-dark-mode/SUMMARY.md
#   docs/plans/260306-1445-dark-mode/phase-01-tokens.md
#   docs/plans/260306-1445-dark-mode/phase-02-components.md
# Ends with: "Use /clear then /execute-plan docs/plans/... to execute"

# Step 3 — execute the approved plan in a fresh context
/clear
/execute-plan docs/plans/260306-1445-dark-mode/SUMMARY.md

---

Well-defined features or large refactors

write-plan → execute-plan

Use when the task is clear but too large or risky to implement without a plan.