@@ -46,7 +46,12 @@ Follow these steps in order:
4646
4747### Step 1: Read the issue
4848
49+ ``` bash
50+ gh issue view " $ISSUE_URL " --json labels,body,comments
51+ ```
52+
4953Extract key information:
54+ - Current labels on the issue
5055- Reproduction steps
5156- Version number (e.g., ` v9.3.1-0 ` )
5257- Reproducible on staging? Production? Both?
@@ -109,7 +114,20 @@ See Decision Tree below for label actions.
109114
110115### Step 7: Post comment and update labels
111116
112- Post your findings and apply appropriate label changes.
117+ Post your findings (use single quotes for the body to handle special characters):
118+ ``` bash
119+ gh issue comment " $ISSUE_URL " --body ' ## 🔍 Investigation Summary
120+ ...your comment here...
121+ '
122+ ```
123+
124+ Remove label only if the decision tree warrants it:
125+ ``` bash
126+ removeDeployBlockerLabel.sh " $ISSUE_URL " DeployBlockerCash # For Backend bugs
127+ removeDeployBlockerLabel.sh " $ISSUE_URL " DeployBlocker # For Frontend bugs
128+ ```
129+
130+ Call scripts by name only (e.g., ` removeDeployBlockerLabel.sh ` ), not with full paths.
113131
114132---
115133
@@ -193,6 +211,7 @@ Technical explanation of what went wrong in the code.
193211- Make assumptions about code you haven't read
194212- Recommend DEMOTE for bugs affecting core functionality (auth, payments, data loss)
195213- Close the issue—only update labels and comment
214+ - Use heredocs, temp files, or shell redirects for comments
196215
197216** DO:**
198217- Always verify the causing PR touches the affected code before concluding
@@ -209,35 +228,3 @@ Technical explanation of what went wrong in the code.
209228- ** Unclear if frontend/backend** : Keep BOTH labels until confirmed
210229- ** Low confidence** : Do NOT remove any labels
211230
212- ---
213-
214- ## Command Reference
215-
216- ** Important:**
217- - Do not use heredocs, temp files, or shell redirects. Pass the comment body directly to ` gh issue comment --body ` .
218- - Call scripts by name only (e.g., ` removeDeployBlockerLabel.sh ` ), not with full paths. The ` .claude/scripts/ ` directory is in PATH.
219-
220- ``` bash
221- # Check current labels on the issue
222- gh issue view " $ISSUE_URL " --json labels --jq ' .labels[].name'
223-
224- # Get StagingDeployCash checklist
225- gh issue list --label " StagingDeployCash" --state open --json number,body --limit 1
226-
227- # View a PR's details
228- gh pr view < PR_NUMBER> --json title,body,author,files,mergedAt
229- gh pr diff < PR_NUMBER>
230-
231- # Verify the PR touches affected code
232- git log --oneline -10 -- < affected_file>
233- gh pr view < PR_NUMBER> --json files --jq ' .files[].path'
234-
235- # Post your findings (use single quotes for the body)
236- gh issue comment " $ISSUE_URL " --body ' ## 🔍 Investigation Summary
237- ...your comment here...
238- '
239-
240- # Remove label (only if decision tree warrants it)
241- removeDeployBlockerLabel.sh " $ISSUE_URL " DeployBlockerCash # For Backend bugs
242- removeDeployBlockerLabel.sh " $ISSUE_URL " DeployBlocker # For Frontend bugs
243- ```
0 commit comments