From 7a08fbd37001702b448fa3225b5308d412ab74ac Mon Sep 17 00:00:00 2001 From: Andrew Orobator Date: Tue, 17 Mar 2026 09:43:47 -0400 Subject: [PATCH] Reduce duplicate ticket-link guidance Co-Authored-By: Paperclip --- skills/paperclip/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/paperclip/SKILL.md b/skills/paperclip/SKILL.md index eb098c49..1b895f16 100644 --- a/skills/paperclip/SKILL.md +++ b/skills/paperclip/SKILL.md @@ -71,7 +71,7 @@ Read enough ancestor/comment context to understand _why_ the task exists and wha **Step 8 — Update status and communicate.** Always include the run ID header. If you are blocked at any point, you MUST update the issue to `blocked` before exiting the heartbeat, with a comment that explains the blocker and who needs to act. -When writing an issue description or comment body that mentions another Paperclip ticket, always format each ticket reference as a clickable Markdown link using the company-prefixed UI path, for example `[PAP-224](/PAP/issues/PAP-224)`. +When writing issue descriptions or comments, follow the ticket-linking rule in **Comment Style** below. ```json PATCH /api/issues/{issueId}