Agent Smith: One Command To Scaffold MCP Servers, Skills, And A Ticket-To-PR Pipeline For Claude Code

Every time you start a new project with Claude Code, do you spend an hour wiring up 11 different MCP servers across 3 JSON files, writing skills that reference your actual commands, and explaining your team's conventions — only to repeat it all on the next project? That's the pain that drove Agent Smith, a new open-source tool that automates the entire Claude Code project setup.

One Command Setup

Run:

npx gunesbizim/agent-smith init

It scans your repo, figures out your actual stack (tested on a Go/Echo + React/Zustand monorepo — nailed everything down to exact versions like golang-jwt, pgx, go-redis), asks a handful of questions about your team's conventions, and then sets up:

• MCP servers
• Hooks
• Skills
• Architecture docs

The skills it generates are not generic slop. For example, the pre-push gate came out as:

golangci-lint run + go test ./... + biome check + vitest run + tsc --noEmit

It actually knew what you were running instead of vomiting Django/pytest defaults.

Autonomous Ticket-to-PR Pipeline

Agent Smith includes an autonomous pipeline: feed it a Jira ticket, and it does plan → implement → test → review → document → PR. It reads what depends on what before touching code, does symbol-level edits instead of yolo find-and-replace, drives the app in a real browser for screenshots, and runs static analysis before the PR. After setup, restart Claude Code and you'll have /backend, /frontend, /test, /pr-review commands ready to go.

Open Source & Free

Agent Smith is MIT licensed, open source, and free. The creator is asking for brutally honest feedback — especially on whether the full ticket-to-PR pipeline holds up on bigger/messier codebases or where it falls over.

Repo: github.com/gunesbizim/agent-smith