auto-setup — Claude Code skill: instant project configuration
The auto-setup skill detects your project type and automatically configures linters, type checking, tests, and formatting. Use it when starting work on an unfamiliar codebase.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat auto-setup does
auto-setup examines your project's config files—package.json, pyproject.toml, Cargo.toml, go.mod—to determine the language and runtime. It then generates the appropriate quality gates: linting, type checking, testing, and code formatting. Each language gets its own toolchain: npm and TypeScript for JavaScript, ruff and mypy for Python, cargo clippy for Rust, golangci-lint for Go.
The skill verifies that required tools are installed and reports missing ones with installation instructions. Results go into .claude/settings.json with pre-configured permission rules. Existing settings are never overwritten without your approval.
Ideal for your first day in a new repository or when adding CI/CD integration. One request sets up code quality checks across the board—linters catch issues, tests run in Claude Code, formatting stays consistent.
What it helps with
- set up linting and formatting for a new project
- automatically select tools based on programming language
- verify required dependencies for code quality checks are present
- generate configuration with commands for all development stages
Example prompts for the agent
- Set up code quality gates for this project automatically
- Detect the project type and configure quality gates
- Create
.claude/settings.jsonwith lint and test commands
How to install auto-setup
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill auto-setup -a claude-code3Manually: put the files in place
~/.claude/skills/auto-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/auto-setup/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill auto-setup -a codex2Manually: put the files in place
.agents/skills/auto-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill auto-setup -a cursor2Manually: put the files in place
.cursor/skills/auto-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/auto-setup2Manually: put the files in place
.github/skills/auto-setup/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill auto-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/auto-setupManually: put the files in place
.devin/skills/auto-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about auto-setup
How do I install auto-setup in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. Next, execute npx skills add rohitg00/pro-workflow --skill auto-setup -a claude-code — the skill will be available at ~/.claude/skills/auto-setup/SKILL.md.
What does auto-setup do?
It identifies your project's programming language, selects matching tools for linting and testing, checks whether they're installed, and writes the commands to a configuration file.
What if my project already has settings configured?
The skill requests permission before overwriting—your existing settings remain untouched unless you approve the change.
Source text
SKILL.md · MIT
---
name: auto-setup
description: Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
user-invocable: true
---
# Auto Setup
Detect project type and configure pro-workflow quality gates automatically.
## Trigger
Use when:
- Starting work on a new project
- Onboarding to an unfamiliar codebase
- Setting up CI integration
## Detection
### Step 1: Identify Project Type
```bash
ls package.json pyproject.toml Cargo.toml go.mod Gemfile pom.xml build.gradle 2>/dev/null
```
### Step 2: Configure Quality Gates
**Node.js/TypeScript:**
```json
{
"lint": "npm run lint",
"typecheck": "npx tsc --noEmit",
"test": "npm test -- --changed --passWithNoTests",
"format": "npx prettier --check ."
}
```
**Python:**
```json
{
"lint": "ruff check .",
"typecheck": "mypy .",
"test": "pytest --tb=short -q",
"format": "ruff format --check ."
}
```
**Rust:**
```json
{
"lint": "cargo clippy -- -D warnings",
"typecheck": "cargo check",
"test": "cargo test --quiet",
"format": "cargo fmt --check"
}
```
**Go:**
```json
{
"lint": "golangci-lint run",
"typecheck": "go vet ./...",
"test": "go test ./... -count=1",
"format": "gofmt -l ."
}
```
### Step 3: Verify Tools Are Installed
Run each command with `--version` or `--help` to confirm availability. Report missing tools.
### Step 4: Create Configuration
Generate a `.claude/settings.json` with:
- Quality gate commands for the detected project type
- Suggested permission rules (user reviews and approves)
- Hook configuration for the project
## Output
```text
AUTO SETUP
Project type: [Node.js/Python/Rust/Go/Mixed]
Package manager: [npm/pnpm/yarn/pip/cargo]
Quality gates configured:
lint: [command] ✓
typecheck: [command] ✓
test: [command] ✓
format: [command] ✓
Missing tools:
- [tool] — install with: [command]
Settings written to: .claude/settings.json
```
## Rules
- Never overwrite existing settings without asking
- Detect, don't assume — check for tool presence
- Support monorepos (check for workspaces config)
- Report missing tools with install commands
© Rohit Ghumare · MIT · rohitg00/pro-workflow