siege-analytics

Environment Preflight Rules — Testing skill for Claude Code

Testing community

Always-on. Before writing or testing code in a repo not yet inventoried this session, run an environment preflight.

How to install Environment Preflight Rules

Installs to ~/.claude/skills/siege-analytics-claude-configs-public-_environment-preflight-rules/SKILL.md

Terminal

mkdir -p ~/.claude/skills/siege-analytics-claude-configs-public-_environment-preflight-rules && curl -fsSL https://raw.githubusercontent.com/siege-analytics/claude-configs-public/HEAD/skills/_environment-preflight-rules.md -o ~/.claude/skills/siege-analytics-claude-configs-public-_environment-preflight-rules/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Environment Preflight Rules does

description: Always-on. Before writing or testing code in a repo not yet inventoried this session, run an environment preflight. Skipping is allowed but must be explicit. Came out of a session where the agent claimed Spark and pyspark were unavailable when they were installed under pyenv and orchestrated by the user's SZSH config.

Environment preflight

Before substantive code or test work in a repository the agent has not touched in this session, run an inventory of what is actually

Alternatives in Testing

Deslop Reborn — One iteration of the IronClaw Reborn de-slop loop — take ONE Reborn crate, fan out parallel review sub-agents 12.6k ★
Factory — Dark Factory Mode - Spec-in, software-out autonomous pipeline 2.8k ★
Claude Codepro — by Max Ritter - Professional development environment for Claude Code with spec-driven workflow, TDD enforcemen 1.6k ★