What is sync-issue-title-and-detail-to-this-pr?

A workflow for keeping a pull request's title and summary aligned with its parent GitHub issue. A pull request is a proposed code change, while an issue tracks the work or problem behind it.

Use it to copy a pull request's title and summary to its issue, or create and link an issue from the pull request.

It prevents the issue and code review from describing different work. It also handles creating and linking a parent issue when one is missing, with approval before writing to GitHub.

sync-issue-title-and-detail-to-this-pr — Skill for Claude Code and Cod

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add aiya000/dotfiles --skill sync-issue-title-and-detail-to-this-pr

Clone the repo

git clone --depth 1 https://github.com/aiya000/dotfiles

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr/github.svg)](https://agentmods.dev/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr)

Your own site

<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-issue-title-and-detail-to-this-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,703 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00081	$0.01703
Opus 5	$0.00041	$0.00851
Sonnet 5	$0.00016	$0.00341
Haiku 4.5	$0.00008	$0.00170

Measured 3d ago against content hash 6f5bb0d62446, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sync-issue-title-and-detail-to-this-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.kiro_global/skills/sync-issue-title-and-detail-to-this-pr/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRのタイトルと概要を親Issueへ同期

目的

PRを正として、親Issueのタイトルと概要を同期する。

親Issueが未リンクの場合は、PRのタイトルと概要からIssueを新規作成し、PRへリンクする
親Issueが存在する場合は、Issueのタイトルと本文だけをPRに合わせて更新する

GitHubへの書き込み前に、必ず同期内容をユーザーへ提示して明示的な承認を得る。

入力

PR番号またはURL。省略時は現在のブランチに紐づくPRを使う
対象リポジトリ。省略時は現在のリポジトリを使う

手順

1. PR情報を取得する

対象リポジトリと gh auth status を確認する
PR番号が指定されていない場合は、gh pr view --json number -q .number で現在のブランチに紐づくPR番号を取得する
gh pr view <PR> --json number,title,body,url でPRのタイトル、本文、URLを取得する
PRを特定できない場合は、ユーザーにPR番号またはURLを確認する

2. 親Issueを特定する

PR本文から、次のパターンを大文字小文字を区別せず検索する。

Close #N、Closes #N、Closed #N
Fix #N、Fixes #N、Fixed #N
Resolve #N、Resolves #N、Resolved #N
Issue: #N、Issue: Closes #N、- Issue: #N

複数のIssue番号が見つかった場合は、更新対象をユーザーへ確認する
1件見つかった場合は、gh issue view <番号> --json number,title,body,url,labels,assignees で現在のIssueを取得する
見つからない場合は「親Issueを新規作成する」へ進む

3. 親Issueを新規作成する

.github/ISSUE_TEMPLATE/default.md と適用される AGENTS.md を読む
次の内容を組み立てる
- Issueタイトル: PRタイトルをそのまま使用
- 「何に貢献するか」: PR本文から該当項目を判断。判断できない場合はユーザーへ確認
- 「本文」: PR本文の ## 変更の目的と背景 セクション。存在しない場合はPR本文冒頭の概要
- 現行規約で必須の手動動作確認手順などがあれば、その形式も満たす
新しいIssueのタイトルと本文をユーザーへ全文提示する
PR本文へ追加する Closes #<新Issue番号> の位置と、既存本文を保持することを説明する
ユーザーの明示的な承認を待つ。承認前にIssue作成やPR更新をしない
承認後、Markdown本文を --body-file で渡して gh issue create を実行する
新Issue番号を取得し、PR本文の ### 関連するIssue・タスク に Closes #<新Issue番号> を追記する
セクションが存在しない場合は、既存本文を削除せず適切な位置に関連Issueセクションを追加する
PR本文も --body-file で安全に渡し、gh pr edit <PR> で更新する
IssueとPRを再取得し、作成内容とリンクを検証する
新規作成フローを完了し、既存Issueの更新フローは実行しない

4. 既存Issueへの同期内容を組み立てる

新タイトルはPRタイトルをそのまま使用する
PR本文から、次の優先順で概要を抽出する
1. ## 変更の目的と背景 セクションの内容
2. PR本文冒頭から最初の ## 見出しまでのテキスト
3. どちらもない場合は、PR本文全体の先頭200文字から作る事実に基づく要約
既存Issue本文に「何に貢献するか」などのチェックリストがある場合は、その内容とチェック状態を保持する
チェックリスト以降の本文部分をPR概要で置き換える
チェックリストがない場合はPR概要だけで本文を構成する
PR本文全体をそのままIssueへコピーしない

5. 差分を提示して承認を得る

次をユーザーへ提示する。

対象PRとIssueのURL
タイトル: [旧] から [新] への差分
組み立てた新しいIssue本文の全文
変更しないラベル、アサイニー、その他の属性

Read the full file on GitHub · 109 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 109 lines · 81 tokens per session scan A 6f5bb0d62446

Subscribe to this mod's changes

sync-issue-title-and-detail-to-this-pr is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 1,703 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.

Git and workflow Project management clojure dotfiles neovim vim xmonad

autopilot

Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).

joshukraine/dotfiles · 40 tokens

autopilot-triage

Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.

joshukraine/dotfiles · 44 tokens

create-pr

Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.

joshukraine/dotfiles · 25 tokens

write-ticket-description

Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.

ooloth/dotfiles · 64 tokens

use-trekker

Full reference for the trekker task management workflow. Use when working with trekker issues, planning multi-step work, or managing task lifecycle.

ooloth/dotfiles · 33 tokens

use-beads

Full reference for the beads task management workflow. Use when working with beads issues, planning multi-step work, or managing task lifecycle.

ooloth/dotfiles · 30 tokens