Skip to content
Skills Library
Programming · Automation

link

/link

(forwward) Keeps every PR linked to a tracker issue — detects the project's tracker (Linear, Jira, or GitHub Issues), validates the PR body has a closing keyword, and if it's missing, creates the issue and adds the reference. Triggers on "link this PR to a ticket", "make an issue for this", "does this PR have a ticket", or before merging work that has none.

Licence
MIT
Last repository change
30.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

(forwward) Keeps every PR linked to a tracker issue — detects the project's tracker (Linear, Jira, or GitHub Issues), validates the PR body has a closing keyword, and if it's missing, creates the issue and adds the reference. Triggers on "link this PR to a ticket", "make an issue for this", "does this PR have a ticket", or before merging work that has none.

Triggers from the description

link this PR to a ticketmake an issue for thisdoes this PR have a ticket
Original author description

(forwward) Keeps every PR linked to a tracker issue — detects the project's tracker (Linear, Jira, or GitHub Issues), validates the PR body has a closing keyword, and if it's missing, creates the issue and adds the reference. Triggers on "link this PR to a ticket", "make an issue for this", "does this PR have a ticket", or before merging work that has none.

How it works

  1. Step 0 — Detect the tracker (never assume)
  2. Step 1 — Check the PR for a valid link
  3. Step 2 — Create the issue (when missing)
  4. Step 3 — Wire the reference back
  5. Optional: retro sweep
  6. Anti-patterns
Original SKILL.md headings · 69 lines, 500 words
SKILL.md preview
---
name: link
description: (forwward) Keeps every PR linked to a tracker issue — detects the project's tracker (Linear, Jira, or GitHub Issues), validates the PR body has a closing keyword, and if it's missing, creates the issue and adds the reference. Triggers on "link this PR to a ticket", "make an issue for this", "does this PR have a ticket", or before merging work that has none.
---

# Link — Every PR Traces to an Issue

No work should merge untracked. This enforces the convention — a PR links to a tracker issue via a
closing keyword — and closes the gap when one's missing by creating the issue and wiring the reference.

**North star:** every PR body carries a valid `Closes|Refs <ISSUE-KEY>` for the project's actual tracker,
and the issue exists — done with one command, not a manual hunt.

## Step 0 — Detect the tracker (never assume)

Resolve which tracker this repo uses, in order:
- The repo's PR template or contributing doc, if it states a convention.
- Config or references in the repo pointing at a Linear team, a Jira project key, or GitHub Issues.
- If genuinely ambiguous, ask once rather than guessing — creating a ticket in the wrong system is
  worse than asking.

Key formats: Linear uses a team prefix (`TEAM-123`), Jira uses a project key (`PROJ-123`), GitHub Issues
uses `#123` in the same repo or `owner/repo#123` cross-repo.

## Step 1 — Check the PR for a valid link

```bash
gh pr view <num> --json body,title,headRefName
```

Look in the body (and the branch name as a fallback) for a closing keyword + a real issue key:
`Closes|Close|Closed|Fixes|Fix|Fixed|Resolves|Resolve|Resolved|Refs|Ref <KEY>`.

- **Present and the issue exists** (verify against the tracker) → nothing to do, report it.
- **Present but the issue doesn't exist or is in the wrong project** → flag it, treat as missing.
- **Absent** → Step 2.

## Step 2 — Create the issue (when missing)

Draft from the PR, then create it in the detected tracker:
- **Title** — the PR title, tightened to an imperative.
- **Description** — a 2-3 line what/why from the PR body, plus a link back to the PR.
- **Team/project** — the repo's mapped destination; confirm rather than guess if there's more than one.
- **Status/labels** — sensible defaults only (e.g. "In Progress" since a PR already exists) — don't
  over-set fields the team doesn't use.

Capture the returned key.

## Step 3 — Wire the reference back

Add the closing keyword to the PR body so the link is bidirectional and the merge can auto-close the
issue:

```bash
gh pr edit <num> --body "<updated body with 'Closes TEAM-456' appended>"
```

Prefer `Closes`/`Fixes` when the PR fully resolves the issue (auto-closes on merge); use `Refs` when
it's partial. Confirm the tracker now shows the PR linked.

## Optional: retro sweep

To backfill a whole repo: list open PRs, run Steps 1-3 per unlinked PR. Skip drafts and already-linked
PRs.

## Anti-patterns

- Guessing the tracker instead of detecting it from the repo's own convention.
- Creating a duplicate issue when a valid one is already referenced — verify existence first.
- Inventing an issue key instead of creating a real one.
- Over-populating tracker fields; set the minimum that makes it useful.
- Using `Closes` on a PR that only partially addresses the issue (it wrongly auto-closes) — use `Refs`.

Versions

RepositoryScoreLicence
This page · iankiku/forwward-teams100MIT
web3illy/private-second-brain-skills100MIT
atakanelik34/bilinc-memory-history91MIT
learnmore4515-code/OS86MIT

Database snapshot: 13.11.2026 · package version 08b7c848f3e6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100link-ticket-to-session
    Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g.…
  • 100fetch-issues
    Use when the user asks to list, show, or review open issues — from the tracker recorded in docs/agents/issue-tracker.md, whether GitHub, Jira, local markdown, or another backend, or from a repository or project the user names. Read-only: not for creating, editing, closing, or triaging issues.
  • 100link-issue
    Make sure the work in hand has a GitHub issue that its pull request will close — find the planned ticket, file one before starting ad-hoc work, or backfill one for work already done. Use this skill before starting any change that has no ticket, before creating or updating a pull…
  • 100jam-to-ticket
    File a Jam (a jam.dev screen recording with the console, network and user actions attached) as an issue in the team's tracker, such as Linear, GitHub Issues or Jira, with the link, repro steps, the key frame and the errors, after checking it was not filed already. Use when the…
  • 90using-tracker
    Use when the user mentions issues, tickets, tasks, epics, current work, sprint or cycle, backlog, creating or updating issues, or anything about task tracking and planning in any tracker (Linear, Jira, GitHub Issues, local files). Invoke BEFORE asking the user any question about…
  • 100pr-link-issue
    Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.