rohitg00/pro-workflow / skills/auto-setup
auto-setup
VerifiedAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
SKILL.md
View on GitHub---
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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |