Jira Link
Puts the Jira key at the front of PR titles and links the PR back to the issue.
Fonctionne avec configuration
Ce que fait
Normalizes Jira issue keys to the start of GitHub PR titles and adds the PR as a remote link on the linked Jira issue, with status transitions tied to PR/deploy events (develop merge stays Review, only a prod deploy closes the loop). Triggers proactively after PR creation/editing or when a Jira key is mentioned alongside a PR, for GitHub orgs mapped to a Jira project. Actually calling the APIs requires the `gh` CLI, a `jira` CLI (go-jira), and a JIRA_API_TOKEN.
Rapport de test
On a PR titled `fix(BE-111): update auth flow` merged into develop, the skill correctly says leave the title alone and hold BE-111 in Review (not Done) until the prod deploy -- a naive assistant would duplicate the key or close the ticket early -- but it needs the `gh`/`jira` CLIs and a JIRA_API_TOKEN configured before any of that actually runs.
Testé le: 2026-07-15 · Claude Code 2.x (agent harness)
Installation
git clone https://github.com/BrOrlandi/my-claude-skills.git mkdir -p ~/.claude/skills cp -r my-claude-skills/jira-link ~/.claude/skills/jira-link
Commandes et exemples de prompts
/jira-linkPuts the Jira key at the front of PR titles and links the PR back to the issue.
Les skills se déclenchent sur des demandes en langage courant — aucune commande à retenir. Après installation, des prompts comme ceux-ci l'activent (en anglais) :
I just opened a pull request, please link it to the Jira issueBE-123 is what I'm working on, I already have a PR open for itMake sure the PR title has the Jira key at the very front