Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →liferay/test-plan
Generate a targeted local test plan for branch changes.
Passed 9 of 15 test cases with the skill, and 7 of 15 without it.
and 5 more in the full report
8 fixed6 passed either way5 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What header comments must be present at the top of the generated premerge shell script?
| Checked | Without skill | With skill |
|---|---|---|
| Includes git branch name, generation date, commit/file counts, affected areas, and estimated execution time relative to budget | Missed | Passed |
The instructions your model reads when the skill loads.
Produce a runnable shell script that executes the tests most likely to regress given the current branch's changes compared to master.
The full test suite takes hours to run, so the team merges aggressively and relies on a daily full-suite run that delivers results within 24 hours of merge. This skill produces a focused premerge script (under 20 minutes) that mitigates risk without attempting full coverage — its goal is to catch the most likely regressions, not every possible one.
Consult the reference file for detailed test organization patterns:
${CLAUDE_SKILL_DIR}/references/test-organization.md
git diff master...HEAD --name-only
git log master..HEAD --oneline
Read the changed files to understand what the changes actually do — not merely which files were touched, but what behavior changed. This understanding drives the test selection.
Consider the blast radius of each change:
portal-kernel, *-api modules): Anything that depends on the changed API could regress. Search for consumers.The objective is not to "find every test in modules that were touched" — it is to find tests that exercise the code paths that changed.
For each area that could regress, search for test files. Use parallel Agent and Glob calls for speed. Consult ${CLAUDE_SKILL_DIR}/references/test-organization.md for the exact patterns and conventions.
test cases passed, vs 7 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.