From e5b54c24afdd569765b215732884bd0a8f2758a9 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Fri, 24 Apr 2026 19:11:41 -0500 Subject: docs: split Linear vs PR structure; propagate content-scope rule to Tier 1 skills Linear ticket bodies are now Problem + Fix only. PR descriptions keep the four-section format (Problem, Fix, Why this fixes it, How it was tested). Linear's GitHub integration handles the cross-link via the PR body's Linear: line. Cross-ref to the content-scope rule appended at the end of each Tier 1 skill that produces public artifacts: testing.md, arch-document, arch-decide, arch-design, review-code, respond-to-review, brainstorm, codify. Single-source the rule in commits.md, point at it from each output-producing skill. --- respond-to-review/SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'respond-to-review') diff --git a/respond-to-review/SKILL.md b/respond-to-review/SKILL.md index c1cc996..3508fa5 100644 --- a/respond-to-review/SKILL.md +++ b/respond-to-review/SKILL.md @@ -48,3 +48,7 @@ For each review comment, before implementing anything: - Summarize what was implemented, what was deferred, and what needs discussion - Link any follow-up issues created for out-of-scope suggestions + +## Content scope + +Output this skill produces that gets committed or shared with the team must follow the *Content scope for public artifacts* rule in [`commits.md`](../claude-rules/commits.md): no local paths, no private repo names, no personal tooling references. -- cgit v1.2.3