test-suite-setup
Set up test validation commands for any project type. Use when configuring test runners, setting up validation commands for a new project, or enabling closed-loop agent workflows.
What this skill does
# Test Suite Setup Skill Help set up test validation for any project to enable closed-loop workflows. ## When to Use - Setting up validation commands for a new project - Discovering existing test infrastructure - Creating a validation stack for CI/CD or agentic workflows - Standardizing test commands across a codebase ## Setup Workflow ### Step 1: Detect Project Type Look for configuration files to identify the stack: | File | Project Type | | --- | --- | | `package.json` | Node.js / TypeScript | | `pyproject.toml` | Python (modern) | | `requirements.txt` | Python (pip) | | `go.mod` | Go | | `Cargo.toml` | Rust | | `pom.xml` | Java (Maven) | | `build.gradle` | Java (Gradle) | ### Step 2: Identify Existing Test Infrastructure Check for test directories and configurations: ```bash # Common test locations ls -la tests/ test/ __tests__/ spec/ # Check for test config files ls -la pytest.ini jest.config.* vitest.config.* .mocharc.* ``` ### Step 3: Extract Available Commands For Node.js projects: ```bash # Show available npm scripts cat package.json | grep -A 30 '"scripts"' ``` For Python projects: ```bash # Check pyproject.toml for tools cat pyproject.toml | grep -A 10 '\[tool\.' ``` ### Step 4: Generate Validation Commands Create a validation stack appropriate for the project: **Template:** ```markdown ## Validation Commands Execute every command to validate with 100% confidence - `[lint command]` - Code style and syntax - `[type check command]` - Type safety (if applicable) - `[test command]` - Behavior correctness - `[build command]` - Production readiness ``` ## Quick Reference by Stack ### Python (uv + pytest) ```markdown ## Validation Commands - `uv run ruff check .` - Linting - `uv run mypy .` - Type checking - `uv run pytest -v` - Tests ``` ### Python (pip + pytest) ```markdown ## Validation Commands - `flake8 .` or `ruff check .` - Linting - `mypy .` - Type checking - `pytest -v` - Tests ``` ### TypeScript/JavaScript (npm) ```markdown ## Validation Commands - `npm run lint` - ESLint - `npx tsc --noEmit` - Type checking - `npm test` - Tests - `npm run build` - Build verification ``` ### TypeScript (Bun) ```markdown ## Validation Commands - `bun run lint` - Linting - `bun tsc --noEmit` - Type checking - `bun test` - Tests - `bun run build` - Build verification ``` ### Go ```markdown ## Validation Commands - `go fmt ./...` - Formatting - `go vet ./...` - Static analysis - `go test ./... -v` - Tests - `go build ./...` - Build verification ``` ### Rust ```markdown ## Validation Commands - `cargo fmt --check` - Formatting - `cargo clippy` - Linting - `cargo test` - Tests - `cargo build --release` - Build verification ``` ## Fallback: No Test Infrastructure If no test infrastructure exists, recommend setup: ### Python ```bash # Install pytest uv add --dev pytest pytest-cov # Create test directory mkdir tests touch tests/__init__.py touch tests/test_example.py ``` ### TypeScript ```bash # Install vitest (modern, fast) npm install -D vitest # Or Jest npm install -D jest @types/jest ts-jest # Create test directory mkdir __tests__ ``` ## Verification After setup, verify the validation stack works: ```bash # Run each command and confirm success [lint command] # Should exit 0 [type command] # Should exit 0 [test command] # Should exit 0 [build command] # Should exit 0 ``` ## Memory References - @validation-commands.md - Full validation patterns - @test-leverage-point.md - Why tests matter - @closed-loop-anatomy.md - Using tests in feedback loops ## Version History - **v1.0.0** (2025-12-26): Initial release --- ## Last Updated **Date:** 2025-12-26 **Model:** claude-opus-4-5-20251101
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.