PR Body
SAP/spartacus
A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.
Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shopsys/shopsys acceptance-criteria-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .claude/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .claude/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-checkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shopsys/shopsys acceptance-criteria-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .agents/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .agents/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shopsys/shopsys acceptance-criteria-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .cursor/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .cursor/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/shopsys/shopsys.git --path .agents/skills/acceptance-criteria-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shopsys/shopsys acceptance-criteria-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .gemini/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .gemini/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install shopsys/shopsys acceptance-criteria-checkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .github/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .github/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add shopsys/shopsys --skill acceptance-criteria-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install shopsys/shopsys acceptance-criteria-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shopsys/shopsys.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/acceptance-criteria-check .opencode/skills/acceptance-criteria-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "acceptance-criteria-check" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/acceptance-criteria-check into .opencode/skills/acceptance-criteria-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "acceptance-criteria-check", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
acceptance-criteria-checkChecks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.
Acceptance Criteria Check is an agent skill from shopsys/shopsys. Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright. Finds the issue whose "Merge Request" field holds the PR URL, reads its acceptance criteria, verifies each one in the running application (falling back to the diff for criteria that are not visible in a browser), and posts one sticky advisory report with screenshots. Use in CI on pull requests, or locally against a review URL.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories and Pull requests. It works with Playwright, Jira and Git. The repository describes itself as: Main repository for maintaining Shopsys Platform packages. Open for ISSUES and PULL REQUESTS.
Read from SKILL.md and the folder at commit a994ffa. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Acceptance Criteria Check loads about 1k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 533 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 533 words (~1,046 tokens).
“The canonical instructions live in project-base. Read them:”
Just SKILL.md in .agents/skills/acceptance-criteria-check of shopsys/shopsys.
Open the folder on GitHubat commit a994ffa
Acceptance Criteria Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Acceptance Criteria Check this skillshopsys/shopsys | 350 | — | ~1k | Automated safety check: Pass | Custom licence | |
| PR BodySAP/spartacus | 784 | — | ~499 | Automated safety check: Pass | Apache-2.0 | |
| Dispatch Basevfarcic/dot-agent-deck | 109 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Execute Issuelbedner/aegis-stack | 143 | — | ~1.1k | Automated safety check: Pass | MIT | |
| QAwp-media/wp-rocket | 767 | — | ~552 | Automated safety check: Pass | GPL-2.0 | |
| Gitea Workflowjwynia/agent-skills | 170 | — | ~3.8k | Automated safety check: Pass | MIT |
SAP/spartacus
A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.
vfarcic/dot-agent-deck
Bring the base that every dispatched unit is cut from up to date before the first dot-agent-deck dispatch of a batch in this repo, and check the base dispatch reports afterwards.
lbedner/aegis-stack
A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.
wp-media/wp-rocket
Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment.
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
Code-and-Sorts/awesome-copilot-agents
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows.
shopsys/shopsys
Ad-hoc Pull Request Publisher — commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the…
shopsys/shopsys
Interactive commit workflow — analyzes all uncommitted changes, proposes atomic, logically grouped commits with messages following commit-conventions, and executes them only after the user approves…
shopsys/shopsys
Create a Shopsys-style enum (a class extending AbstractEnum with public typed constants, NOT a native PHP enum).
shopsys/shopsys
Searches and analyzes documentation to provide relevant information for development tasks.
shopsys/shopsys
Work with GitHub PR review threads — list unresolved comments as a digest (who is waiting on whom), reply to threads, and resolve/unresolve them.
shopsys/shopsys
Generates a PR description focused on business value using the project's PR template.
Works with
Categories
Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright. Acceptance Criteria Check is an agent skill from shopsys/shopsys. Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.
Acceptance Criteria Check fits situations like: tasks that involve User stories; tasks that involve Pull requests.
Run `npx skills add shopsys/shopsys --skill acceptance-criteria-check -a claude-code`. Or copy the skill folder (.agents/skills/acceptance-criteria-check in shopsys/shopsys) into .claude/skills/acceptance-criteria-check in your project. Claude Code loads it when a task matches its description.
Run `npx skills add shopsys/shopsys --skill acceptance-criteria-check -a codex`. Or copy the skill folder (.agents/skills/acceptance-criteria-check in shopsys/shopsys) into .agents/skills/acceptance-criteria-check in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shopsys/shopsys --skill acceptance-criteria-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/acceptance-criteria-check, .gemini/skills/acceptance-criteria-check, .github/skills/acceptance-criteria-check and .opencode/skills/acceptance-criteria-check in your project.
Going by SKILL.md and its folder, Acceptance Criteria Check needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Acceptance Criteria Check has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Acceptance Criteria Check: PR Body (SAP/spartacus, 784 stars), Dispatch Base (vfarcic/dot-agent-deck, 109 stars), Execute Issue (lbedner/aegis-stack, 143 stars) and QA (wp-media/wp-rocket, 767 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
shopsys (a GitHub organization) maintains it in shopsys/shopsys, which has 350 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 9, 2026.
Source: shopsys/shopsys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.