CH

changed-slice-verify

Efficient validation for specific code segments or diffs.

Install

mkdir -p .claude/skills/changed-slice-verify && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15180" && unzip -o skill.zip -d .claude/skills/changed-slice-verify && rm skill.zip

Installs to .claude/skills/changed-slice-verify

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when validating recent code edits, checking only the touched slice, or deciding which lint, typecheck, test, and E2E commands to run before replying.
153 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Validate recent code edits
  • Check only the touched slice of code
  • Decide which lint commands to run
  • Decide which typecheck commands to run
  • Decide which test commands to run
  • Decide which E2E commands to run

How it works

The skill runs `pnpm agent:validate` with specified files or the staged diff to identify and execute relevant validation tasks, reporting failures and recommending further checks.

Inputs & outputs

You give it
Changed files or current diff
You get back
Executed validation tasks, failed tasks with output, and recommendations for follow-up checks

When to use changed-slice-verify

  • Validating changes before committing
  • Targeting linting to edited files
  • Running tests for a specific feature slice

About this skill

Changed Slice Verify

When To Use

  • After editing code and before replying to the user.
  • When you need a smaller alternative to full-repo validation.
  • When root config, hooks, skills, or package scripts changed.

Procedure

  1. Run pnpm agent:validate -- --files <path1> <path2> when the touched files are known.
  2. Use pnpm agent:validate -- --staged before commit boundaries.
  3. If the validator emits Android or E2E recommendations, run the recommended command only when the changed slice actually touches that surface.
  4. If validation fails, repair the same slice first and rerun the same command.

Outputs

  • Executed validation tasks
  • Failed tasks with tail output
  • Recommendations for heavier follow-up checks

When not to use it

  • When full-repo validation is required
  • When the changed slice does not touch Android or E2E surfaces
  • When the validator does not emit Android or E2E recommendations

Limitations

  • Recommendations for Android or E2E are only run if the changed slice touches that surface
  • Validation failures require repair of the same slice first
  • The skill is a smaller alternative to full-repo validation

How it compares

This skill targets validation to only the changed slice of code, reducing validation time compared to running full-repo checks.

Compared to similar skills

changed-slice-verify side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
changed-slice-verify (this skill)02moNo flagsBeginner
python-testing-patterns772moReviewIntermediate
dependency-upgrade265moReviewIntermediate
test-cases577moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry