pick-integ

Analyze the integration ledger and code changes to prioritize /run-integ commands.

97|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/go-to-k/cdkd --skill pick-integ
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pick-integ
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/pick-integ
Command: npx skills add https://github.com/go-to-k/cdkd --skill pick-integ

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams decide which integration tests to run by evaluating the integration ledger and recent code changes, reducing wasted test costs while maintaining coverage.

Core Features & Use Cases

  • Ledger-driven prioritization: ranks tests by staleness and last results.
  • Code-change mapping: links recent commits to affected tests and areas.
  • Output plan: prints a ready-to-run, copy-pasteable /run-integ plan.
  • Use Case: pre-release planning, post-merge validation, or when coverage decisions are uncertain.

Quick Start

Provide a base-ref (optional) to compare changes, then run the skill to generate a prioritized /run-integ plan.

Frequently Asked Questions about pick-integ

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I select which integration tests to run for a release?

Select integration tests by analyzing the integration ledger and recent code changes to prioritize tests covering modified areas. This approach evaluates staleness and previous test results to reduce wasted test costs while maintaining coverage.

What is ledger-aware test planning for integration tests?

Ledger-aware test planning ranks integration tests by staleness and last execution results to determine execution priority. It links recent code commits to affected tests to ensure validation efforts target the most relevant coverage areas.

How do I map code changes to integration tests for pre-merge validation?

Map code changes to integration tests by providing a base-ref to compare recent commits against. The system identifies affected areas, queries the ledger for matching tests, and outputs a prioritized run-integ command plan for validation.

Does integration test selection work without a base-ref for code change detection?

Integration test selection works without a base-ref, but providing one allows the system to compare changes explicitly. Without a base-ref, the skill still queries the ledger and analyzes recent code changes to generate a prioritized test plan.

What is the best way to reduce integration test costs while maintaining coverage?

The best way to reduce integration test costs is ledger-driven prioritization, which ranks tests by staleness and previous results. By mapping recent code changes to affected areas, you run only the necessary tests to maintain coverage.

What format does the integration test plan output for execution?

The integration test plan outputs a ready-to-run, copy-pasteable list of run-integ commands. This prioritized plan is generated after handling inputs, querying the ledger, and mapping code changes to the affected tests.