/Catalogue/Prompt/rohitg00/rohitg00-pro-workflow-auto-setup

Origin: github

auto-setup

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.

by rohitg00 · updated 1d ago · imported from GitHub

Installs0+0/7d
Security score98/100
Retention 14d0%
GitHub stars2.9K

Skill logic

Execution graph
User message
Prompt rewrites behaviour
Response

SKILL.md

View on GitHub ↗

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

Discussion

No comments yet — start the thread.

Sign in to join the discussion.

/More from rohitg00/pro-workflow

rohitg00· 1d agoCommunity
skill-optimizer

Prompts · JavaScript · v0.1.0

SkillOpt-flavored offline training loop for any SKILL.md. Treats accumulated learn-rule corrections as training trajectories, proposes bounded patches via an optimizer LLM, gates each candidate against a held-out validation set built from the user's own past corrections, and ships only candidates that demonstrably improve the score. Inspired by Microsoft SkillOpt's ReflACT pipeline (rollout → reflect → aggregate → select → update → evaluate) adapted to pro-workflow's SQLite store. Use when a skill has accumulated 8+ learn-rule rows and the user wants the skill itself to get better, not just longer.

#agent-orchestration#ai-agents#ai-coding

0 2.9K
rohitg00· 1d agoCommunity
agent-teams

Prompts · JavaScript · v0.1.0

Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.

#agent-orchestration#ai-agents#ai-coding

0 2.9K
rohitg00· 1d agoSandbox
batch-orchestration

Prompts · JavaScript · v0.1.0

Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.

#agent-orchestration#ai-agents#ai-coding

0 2.9K
rohitg00· 1d agoSandbox
bug-capture

Prompts · JavaScript · v0.1.0

Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".

#agent-orchestration#ai-agents#ai-coding

0 2.9K