jira-link
Skill22 starsChanged 54 days agoNo licenceView on GitHub
Link GitHub PRs to Jira tasks and normalize the Jira key position in PR titles. ALWAYS use this skill proactively, without waiting for the user to ask, in any of these situations: (1) immediately after creating, opening, or pushing a PR (including via /pr or `gh pr create`); (2) whenever a PR title is being set, edited, or proposed and the repo's GitHub org has a Jira project configured; (3) whenever the user mentions a Jira issue key like `PROJ-123` in the same conversation as a PR; (4) when transitioning, commenting on, or updating the status of a Jira issue that may have an associated PR; (5) when the user asks anything resembling "link this PR to Jira", "connect this with the task", "associate the PR with the issue", or similar. Adds the Jira issue key to the START of the PR title (format: `KEY: rest of title`), normalizes any pre-existing key already in the title (e.g. moves `[PROJ-111]` from the end to the start), turns the key mentioned in the PR body into a clickable markdown link to the Jira issue (when the current user authored the PR), and adds the PR URL as a remote link on the Jira issue. Only activates for repositories belonging to GitHub organizations that have a configured Jira project mapping; silently skips otherwise.
- Sends data out
- Commits and pushes
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autonomous-modeSkill
- commitSkill
- jiraSkill
- pr-commentsSkill
- pr-reviewSkill
- pr-screenshotsSkill
- prSkill
- refactor-codeSkill
- refactor-componentsSkill
- releaseSkill
- security-reviewSkill
- slackSkill
- todo-resolverSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

