rohitg00/pro-workflow / skills/auto-setup
auto-setup
UnverifiedAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
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
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:
{
"lint": "npm run lint",
"typecheck": "npx tsc --noEmit",
"test": "npm test -- --changed --passWithNoTests",
"format": "npx prettier --check ."
}
Python:
{
"lint": "ruff check .",
"typecheck": "mypy .",
"test": "pytest --tb=short -q",
"format": "ruff format --check ."
}
Rust:
{
"lint": "cargo clippy -- -D warnings",
"typecheck": "cargo check",
"test": "cargo test --quiet",
"format": "cargo fmt --check"
}
Go:
{
"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
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| algorithmic-artanthropics/skillsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-gainDietrichGebert/ponytailShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact". | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-reviewDietrichGebert/ponytailQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |