Skip to main content
command CX Codex

sync-pr-to-task · qdhenry — Claude Code command: what it does, how to install

sync-pr-to-task connects GitHub pull requests to Linear issues, mapping review statuses and comments bidirectionally.

no license ★ 1,357 updated 2026-03-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/sync-pr-to-task.md
Open on GitHub

What sync-pr-to-task does

The command extracts issue identifiers from branch naming conventions, PR descriptions, and commit cues such as resolves or closes. It matches ticket patterns like ABC-123 alongside web URLs pointing to Linear workspaces.

Once linked, it maps the state of the pull request directly to the tracker. Draft items map to Backlog, merged code flips the ticket to Done, and approved reviews move issues to In Review. It adds metadata blocks, appends PR links into the task body, and assigns dedicated labels on GitHub via the gh utility.

Working executions rely on an authenticated gh installation in your environment. The routine also validates discrepancies between PR assignees and task owners, surfacing mismatches immediately.

What it helps with

  • connect GitHub pull requests to Linear tickets
  • transition Linear issue states from review approvals
  • detect tracker references in branch names automatically
  • spot metadata mismatches between PRs and tasks

Example prompts for the agent

  • Link PR 123 to Linear issue ABC-456
  • Detect Linear task reference for PR 123 and update its state
  • Validate existing links between pull requests and tracker tasks

How to install sync-pr-to-task

Manually: put the files in place

.claude/commands/sync-pr-to-task.md

Call it with /sync-pr-to-task. For all projects use ~/.claude/commands/

Questions about sync-pr-to-task

How to install sync-pr-to-task in Claude Code?

Place the command specification file into .claude/commands/sync-pr-to-task.md in your project.

What does sync-pr-to-task do?

It reads GitHub pull request properties, finds associated Linear issues, and updates states, comments, and labels across both tools.

Which external tools are necessary for this command?

You need an active GitHub CLI gh setup along with configured access to Linear API endpoints.

Similar slash commands

All slash commands for Git and GitHub →

sync-pr-to-task by other authors comes first.

sync-pr-to-task davila7 sync-pr-to-task connects GitHub pull requests with Linear tasks and syncs task state. Use it to keep PR details and task updates together. CX Codex +1 122installs task-from-pr davila7 task-from-pr turns a GitHub pull request into a Linear task, with a size estimate, team assignment and links running both ways. CX Codex +1 133installs linear-task-to-issue davila7 linear-task-to-issue — a slash command that turns a Linear task into a GitHub issue, carrying over fields, links, attachments and comments. Useful when planning lives in Linear and code lives in GitHub. CX Codex +1 129installs sync-todos-to-github alirezarezvani sync-todos-to-github turns a TodoWrite task list into a GitHub planning issue and starts follow-up automation. Useful for sprint plans and saved work checkpoints. CX Codex +1 ★ 907repo stars sync-automation-setup BuildWithClaude Community sync-automation-setup configures automated two-way synchronization between GitHub and Linear. Sets up webhooks, background queues, and GitHub Actions workflows. CX Codex +1 ★ 3,785repo stars project-board-sync ruvnet project-board-sync — a command that keeps a GitHub Projects board in step with agent-swarm tasks: states, agent labels and priorities land in the right columns. CX Codex +1 ★ 850repo stars openai-gh-address-comments OpenAI openai-gh-address-comments — a Claude Code skill that collects and addresses reviewer comments on an open PR for the current branch using gh CLI. It fetches all review threads, summarises each one, and lets you pick which to fix. CX Codex +1 ★ 540repo stars

From the same set112

The whole set →
cloud-architect cloud-architect designs cloud infrastructure on AWS, Azure or GCP: Terraform modules, network layout, cost estimate. Useful when you plan a migration or need to trim a bill. CX Codex ★ 1,357repo stars memory-curator memory-curator manages semantic memory trees, merges related nodes, and creates checkpoints to prevent knowledge loss. CX Codex ★ 1,357repo stars typescript-pro The typescript-pro subagent designs and refactors TypeScript applications for Node.js and browsers. Use it for advanced types, architecture, testing, and large code changes. CX Codex ★ 1,357repo stars cleanup-vibes cleanup-vibes turns a vibecoded repo into something deployable: pulls hardcoded keys into .env, sorts files into folders, writes the README. CX Codex +1 ★ 1,357repo stars nextjs-pro nextjs-pro — a Next.js subagent for architecture, rendering choices, SEO, testing, and performance work across an existing or new application. CX Codex ★ 1,357repo stars retrospective-analyzer retrospective-analyzer pulls sprint numbers from Linear and Git, finds problems that repeat across retros, and drafts action items with owners and dates. CX Codex +1 ★ 1,357repo stars boundary-guardian boundary-guardian monitors reasoning boundaries and detects semantic drift to stop AI hallucinations before invalid statements occur. CX Codex ★ 1,357repo stars react-pro react-pro — a React-focused subagent for building components, refactoring code, and tackling UI problems. It examines existing project patterns and includes testing in its workflow. CX Codex ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open