Skill98 repo starsupdated today

env-setup

The env-setup skill automates initial project configuration by detecting the technology stack through key configuration files like package.json, pyproject.toml, and Cargo.toml, then executing appropriate dependency installation and build verification commands in the correct sequence. Use this during Phase 0 of a new session to prepare a project environment before development work begins.

View source Repository: AutoFyn

Install in Claude Code

Copy

git clone --depth 1 https://github.com/SignalPilot-Labs/AutoFyn /tmp/env-setup && cp -r /tmp/env-setup/autofyn/skills/env-setup ~/.claude/skills/env-setup

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Environment Setup

## Stack Detection

Read these files to understand what needs to be installed:

| File | Indicates |
|------|-----------|
| `package.json` | Node project — run `npm ci` |
| `pyproject.toml` | Python project — run `pip install -e .` or `uv pip install -e .` |
| `requirements.txt` | Python deps — run `pip install -r requirements.txt` |
| `Cargo.toml` | Rust project — run `cargo build` |
| `go.mod` | Go project — run `go mod download` |

Check `CLAUDE.md` and `README.md` first — they may specify exact setup commands.

## Install Order

1. Read project config files
2. Install backend dependencies
3. Install frontend dependencies (if separate)
4. Run the build to verify it works
5. Run tests to verify the environment is healthy

## If Build Fails

- Read the error carefully — most setup failures are missing system deps or wrong versions
- Check if there's a `.tool-versions`, `.nvmrc`, or `Dockerfile` that specifies required versions
- If a dep is missing from the lockfile, do NOT add it yourself — flag it

## Pre-installed Tools

See the verification-rules appended to build/review agent prompts for the full list. Key ones already in the sandbox: `pytest`, `pyright`, `ruff`, `tsc`, `eslint`. Do NOT pip/npm install these.