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.
Find the SSP Jira issue that belongs to a pull request (given a PR number or URL) and report its key details — status, sprint, assignee, and the Merge Request link.
$ npx skills add shopsys/shopsys --skill find-jira-task-by-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shopsys/shopsys find-jira-task-by-pr --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/find-jira-task-by-pr .claude/skills/find-jira-task-by-pr && 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 "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .claude/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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/find-jira-task-by-prType 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 find-jira-task-by-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shopsys/shopsys find-jira-task-by-pr --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/find-jira-task-by-pr .agents/skills/find-jira-task-by-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .agents/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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 find-jira-task-by-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shopsys/shopsys find-jira-task-by-pr --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/find-jira-task-by-pr .cursor/skills/find-jira-task-by-pr && 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 "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .cursor/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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/find-jira-task-by-pr--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 find-jira-task-by-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shopsys/shopsys find-jira-task-by-pr --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/find-jira-task-by-pr .gemini/skills/find-jira-task-by-pr && 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 "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .gemini/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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 find-jira-task-by-prInstalls 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 find-jira-task-by-pr -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/find-jira-task-by-pr .github/skills/find-jira-task-by-pr && 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 "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .github/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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 find-jira-task-by-pr -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 find-jira-task-by-pr --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/find-jira-task-by-pr .opencode/skills/find-jira-task-by-pr && 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 "find-jira-task-by-pr" agent skill from https://github.com/shopsys/shopsys/tree/20.0/.agents/skills/find-jira-task-by-pr into .opencode/skills/find-jira-task-by-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-jira-task-by-pr", 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.
find-jira-task-by-prFind the SSP Jira issue that belongs to a pull request (given a PR number or URL) and report its key details — status, sprint, assignee, and the Merge Request link.
Find Jira Task By PR is an agent skill from shopsys/shopsys. Find the SSP Jira issue that belongs to a pull request (given a PR number or URL) and report its key details — status, sprint, assignee, and the Merge Request link. Use when the user asks which Jira issue tracks a PR, or invokes /find-jira-task-by-pr.
Its SKILL.md is about 880 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 Development, covering Pull requests. It works with Jira. The repository describes itself as: Main repository for maintaining Shopsys Platform packages. Open for ISSUES and PULL REQUESTS.
3 steps, taken from the step headings in SKILL.md.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comshopsys.atlassian.netFrom 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.
Find Jira Task By PR loads about 884 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 417 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 417 words (~884 tokens).
“Resolves the SSP Jira issue belonging to a pull request and reports what it found. Read-only — never creates, edits, or transitions anything. Requires a connected Jira MCP server.”
Just SKILL.md in .agents/skills/find-jira-task-by-pr of shopsys/shopsys.
Open the folder on GitHubat commit a994ffa
Find Jira Task By PR 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 |
|---|---|---|---|---|---|---|
| Find Jira Task By PR this skillshopsys/shopsys | 350 | — | ~884 | Automated safety check: Pass | Custom licence | |
| PR BodySAP/spartacus | 784 | — | ~499 | Automated safety check: Pass | Apache-2.0 | |
| Link Ticket To SessionJayantDevkar/claude-code-karma | 329 | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Dynamo PR DescriptionDynamoDS/Dynamo | 2k | — | ~880 | Automated safety check: Pass | Apache-2.0 | |
| Review PRlinuxfoundation/insights | 282 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Code Reviewsortie-ai/sortie | 197 | — | ~2.9k | 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.
JayantDevkar/claude-code-karma
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.
DynamoDS/Dynamo
Generate PR descriptions for Dynamo that align with the team template section names and order.
linuxfoundation/insights
Review a pull request against Insights architecture standards — fetches PR diff, verifies previous comments are addressed, validates PR metadata (title, branch, JIRA, size), runs a code-standards…
sortie-ai/sortie
Reviews pull requests in this repository for the defect classes a mechanical checklist misses: documentation that outlived the code it describes, reaction and retry state that leaks or clobbers a…
chef/chef-web-docs
Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.
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
Find the SSP Jira issue that belongs to a pull request (given a PR number or URL) and report its key details — status, sprint, assignee, and the Merge Request link. Find Jira Task By PR is an agent skill from shopsys/shopsys. Find the SSP Jira issue that belongs to a pull request (given a PR number or URL) and report its key details — status, sprint, assignee, and the Merge Request link.
Find Jira Task By PR fits situations like: the user asks which Jira issue tracks a PR; invokes /find-jira-task-by-pr.
Run `npx skills add shopsys/shopsys --skill find-jira-task-by-pr -a claude-code`. Or copy the skill folder (.agents/skills/find-jira-task-by-pr in shopsys/shopsys) into .claude/skills/find-jira-task-by-pr in your project. Claude Code loads it when a task matches its description.
Run `npx skills add shopsys/shopsys --skill find-jira-task-by-pr -a codex`. Or copy the skill folder (.agents/skills/find-jira-task-by-pr in shopsys/shopsys) into .agents/skills/find-jira-task-by-pr 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 find-jira-task-by-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-jira-task-by-pr, .gemini/skills/find-jira-task-by-pr, .github/skills/find-jira-task-by-pr and .opencode/skills/find-jira-task-by-pr in your project.
SKILL.md names no scripts, command-line tools or credentials: Find Jira Task By PR is instructions for the agent only.
SKILL.md names 2 domains. In commands or code: github.com and shopsys.atlassian.net; the agent is likely to contact these when it follows the instructions. 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.
Find Jira Task By PR has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 884 tokens (SKILL.md is roughly 3.5k 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 Find Jira Task By PR: PR Body (SAP/spartacus, 784 stars), Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars), Dynamo PR Description (DynamoDS/Dynamo, 2k stars) and Review PR (linuxfoundation/insights, 282 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.