repo-tooling

Repository Tooling Setup

Configures projects with professional development tooling based on detected language:

• TypeScript/Next.js: ESLint, Prettier, Husky, GitHub Actions
• Python: Ruff, MyPy, pre-commit, GitHub Actions (templates coming soon)

For language detection:

• JavaScript/TypeScript: package.json exists
• TypeScript specifically: tsconfig.json or .ts files present
• Next.js framework: next.config.js or next.config.mjs exists
• Python: pyproject.toml, setup.py, or requirements.txt exists
• Python framework: settings.py (Django), main.py with FastAPI imports, etc.

For existing tooling:

• Linting: eslint.config.mjs, .eslintrc.*, pyproject.toml with [tool.ruff]
• Formatting: .prettierrc, prettier.config.*, pyproject.toml with [tool.black]
• Type checking: tsconfig.json with strict, mypy.ini, pyproject.toml with [tool.mypy]
• Git hooks: .husky/ directory, .pre-commit-config.yaml
• CI/CD: .github/workflows/ directory
• Package manager: Lock files (pnpm-lock.yaml, package-lock.json, yarn.lock, poetry.lock, requirements.txt)

Store findings for recommendation phase.

For TypeScript/JavaScript projects:

1. Check package.json engines.node field first (respect existing constraints)
2. If not specified, fetch latest LTS Node version:
   • Use WebFetch on https://nodejs.org/dist/index.json
   • Find latest entry where lts property is not false
   • Extract major version number (e.g., 22 from v22.12.0)
3. Fall back to current installed version: node --version
4. Store as NODE_VERSION for GitHub Actions workflow

For Python projects (future):

1. Check pyproject.toml python requirement or .python-version file
2. If not specified, fetch latest stable Python version from python.org
3. Fall back to current installed: python --version
4. Store as PYTHON_VERSION for GitHub Actions

Detect package manager from lock files and configuration:

• pnpm: pnpm-lock.yaml exists, extract version from packageManager field if available
• npm: package-lock.json exists
• yarn: yarn.lock exists
• poetry: poetry.lock exists
• pip: requirements.txt exists

Package versions (eslint, prettier, ruff, etc.) use caret ranges in templates - let package manager resolve to latest compatible.

For TypeScript/Next.js projects:

"I can set up professional development tooling for this {framework} project:

{List what will be added based on what's missing:} ✓ ESLint 9 + Prettier 3 for code quality ✓ TypeScript strict mode for enhanced type safety ✓ Pre-commit hooks (Husky + lint-staged) - auto-fix on commit ✓ Pre-push validation (type-check, format, test) ✓ GitHub Actions CI/CD (build, test, quality checks) ✓ Claude Code review on pull requests

Configuration:

• Node.js {detected-version} ({source: from package.json engines / latest LTS / installed})
• {detected-package-manager} {version}
• Latest stable packages: eslint@^9, prettier@^3, husky@^9

{If any tooling already exists:} Already configured: {list existing tools} Will preserve your existing configurations and add missing pieces."

For Python projects:

"Python project detected. Templates for Python tooling setup are coming soon. For now, I recommend manually setting up: ruff for linting, black for formatting, mypy for type checking, and pre-commit for git hooks."

Use AskUserQuestion with single decision point:

• Header: "Setup"
• Question: "Proceed with this setup?"
• Options:
  • "Yes, set it up" - Description: "Use these recommendations and proceed immediately"
  • "Let me customize" - Description: "Choose which features to enable and git strategy"
• multiSelect: false