From 66b44051c5fac48cf53ada8a7f807b7926274169 Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Sat, 25 Jul 2026 08:36:32 -0700
Subject: [PATCH] style(skills): fix prettier emphasis-marker formatting in
 gardening reference.md

#8156 merged before its own follow-up commit (asterisk -> underscore emphasis
markers, prettier's preferred style) could land, leaving main's format:check
red. This is that fix, applied directly against main's current content.
---
 .claude/skills/contributor-pipeline-gardening/reference.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.claude/skills/contributor-pipeline-gardening/reference.md b/.claude/skills/contributor-pipeline-gardening/reference.md
index 9f78e2dc6..96a621d61 100644
--- a/.claude/skills/contributor-pipeline-gardening/reference.md
+++ b/.claude/skills/contributor-pipeline-gardening/reference.md
@@ -120,8 +120,8 @@ path of resistance and submit the shittiest / lowest quality stuff possible to g
 fast as possible unless we are extremely explicit on exactly what we expect... I expect the entire
 issue done flawlessly start to finish, not broken up into smaller pieces and nothing skipped."
 
-This extends the "Reuse-existing-pattern is mandatory" rule above from *which shape to follow* to
-*how much of it must ship*. Every generated issue must leave zero room for a contributor's AI-harness
+This extends the "Reuse-existing-pattern is mandatory" rule above from _which shape to follow_ to
+_how much of it must ship_. Every generated issue must leave zero room for a contributor's AI-harness
 agent to rationally conclude that implementing a subset of the Deliverables checklist, or the
 laziest-possible interpretation of a Requirement, satisfies the issue.
 
@@ -141,7 +141,7 @@ laziest-possible interpretation of a Requirement, satisfies the issue.
 - **Don't under-scope a coherent unit of work just to make the issue look more approachable** — an
   issue whose own Requirements are incomplete, or whose Deliverables can be half-satisfied and still
   plausibly read as "done," invites exactly the shortcut-taking this section exists to prevent. This is
-  separate from splitting a genuinely large epic into multiple *sequential, individually-complete*
+  separate from splitting a genuinely large epic into multiple _sequential, individually-complete_
   issues (e.g. the `types-epic B batch N` family) — each batch issue is itself fully scoped and
   independently completable end to end, and that decomposition is fine. What's not fine is a single
   issue that itself ships incomplete or half-satisfiable.