Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →liferay/pr
Create a GitHub PR for the current branch.
Passed 19 of 22 test cases with the skill, and 9 of 22 without it.
and 10 more in the full report
11 fixed8 passed either way2 still failing1 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
The branch commit references Task issue `LPD-54321` (type ID `10002`), which has a Technical Task subtask (`10153`). Which issue receives status transitions and the PR URL?
| Checked | Without skill | With skill |
|---|---|---|
| Targets the Technical Task subtask rather than the parent Task. | Missed | Passed |
The instructions your model reads when the skill loads.
Create a GitHub PR for the current branch, transition the linked Jira tickets to review, and record the PR URL on those tickets.
The base branch is master in liferay/liferay-portal and master-private in liferay/liferay-portal-ee. Use the base branch of the repository that a remote of this checkout points at (check git remote --verbose).
Below, ${BASE_BRANCH} stands for that base branch, and <repository> stands for that repository without its organization, such as liferay-portal.
At least one commit adds tests. When none do, ask the user for a rationale and refuse to proceed without one. The only exceptions are PRs with no code changes (e.g., language key updates or markdown changes).
The current branch is a development branch, not ${BASE_BRANCH} or any other protected branch.
The pr-check skill must pass. Skip only when ${ARGUMENTS} contains --skip-pr-check. A skip requires a reason: take it from the text following the flag when present, otherwise prompt the user for one. The reason is recorded in the PR Check section, which is written for a skip rather than omitted.
The current Git branch must contain the commits ready to ship.
A branch may span more than one ticket. Resolve the ticket set — every ticket the PR touches.
The ticket key follows the pattern LPD-12345, LCD-12345, LRCI-1234, and similar forms (uppercase letters, hyphen, digits).
Collect every distinct ticket key from the subjects of the branch's commits relative to ${BASE_BRANCH}. Each subject is prefixed with its ticket (LPD-12345 <subject>); extract every distinct key, in commit order (oldest first). When no commit carries a ticket, prompt the user for one.
The target repository defaults to <fork-owner>/<repository>. When ${ARGUMENTS} names a different org/repo, use that; when it matches an alias below, expand the alias; otherwise, ask the user to choose <fork-owner> from the teams below, leaving out any team that has no fork of <repository>:
liferay-acliferay-appsecliferay-bpmliferay-commercetest cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.