analysis-target Repository Skill

analysis-target Repository Skill

Use When

• You are working inside analysis-target.

• You need repository-specific commands, validation checks, or configuration references.

• You want evidence-backed onboarding context instead of inferred workflow assumptions.

• Root Directory: ./tests/fixtures/analysis-target

• Detected Package Manager: pnpm

Steps

• Review relevant config files first: .env.example, package.json, vite.config.ts.
• Start code navigation from evidenced directories: src.
• Use only the detected commands below; do not invent package scripts.
• Before finishing, run the relevant validation commands listed below.

Maintenance Workflow

Before Editing

• Treat repository files as evidence; inspect the relevant source and config before changing behavior.
• Do not trust generated instructions blindly; compare them against the referenced repository files.

Implementation Discipline

• Keep changes scoped to the requested behavior and the files directly needed for that behavior.
• Match local patterns before introducing new abstractions.
• Do not invent package scripts, entrypoints, or environment variables that are not evidenced below.

Validation Ladder

• Run the narrowest relevant detected check first.
• Broaden to additional detected checks when touching shared code, config, or public behavior.
• Report any checks that could not be run.

When Tests Are Missing

• Use the smallest reproducible manual check tied to the changed behavior.