Address review: capture FOLLOW_UP_URL, sync jq parens, tighten check-all-reviews

- Capture gh issue create output into FOLLOW_UP_URL in Step 9 so Step 10's
  summary comment can include the link (was previously unset).
- Add a "Capture the gh issue create output into FOLLOW_UP_URL" rule line so
  followers don't miss the assignment.
- Drop the redundant MUST_FIX_BLOCK alias and use MUST_FIX_SECTION directly in
  the empty check and for-loop.
- Sync prompts/address-review.md jq select expression with commands/ by
  removing redundant outer parens.
- Tighten check-all-reviews matching in both files: case-insensitive, trailing
  position only; warn on leading/embedded usage instead of silently falling
  through to a cutoff-filtered scan.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: justin808

commands/address-review.md

@@ -10,9 +10,10 @@ Fetch review comments from a GitHub PR in this repository, triage them, and crea
 
 The user's input is: $ARGUMENTS
 
-First, detect whether the request includes the exact phrase `check all reviews`.
+First, detect whether the request includes the phrase `check all reviews` (case-insensitive, trailing position only — match it as the final tokens of the input, after the PR reference).
 
 - If it does, set a `CHECK_ALL_REVIEWS` flag and remove only that phrase before parsing the PR reference.
+- If the phrase appears in any other position (leading, embedded), do not treat it as an override; warn the user and ask them to retry with the trailing form.
 - Mention that override in the eventual PR summary comment so future runs have clear history.
 
 Then extract the PR number and optional review/comment ID from the remaining input:
@@ -323,8 +324,6 @@ MUST_FIX_SECTION="$(cat <<'EOF'
 EOF
 )"
 
-MUST_FIX_BLOCK="${MUST_FIX_SECTION}"
-
 DISCUSS_SECTION=""
 if [ -n "${DISCUSS_ITEMS}" ]; then
   DISCUSS_SECTION="### Discuss items
@@ -339,11 +338,11 @@ ${SKIPPED_ITEMS}
 "
 fi
 
-if [ -z "${MUST_FIX_BLOCK}${DISCUSS_SECTION}${SKIPPED_SECTION}" ]; then
+if [ -z "${MUST_FIX_SECTION}${DISCUSS_SECTION}${SKIPPED_SECTION}" ]; then
   echo "No deferred items found; skip follow-up issue creation."
 else
   SECTION_CONTENT=""
-  for section in "${MUST_FIX_BLOCK}" "${DISCUSS_SECTION}" "${SKIPPED_SECTION}"; do
+  for section in "${MUST_FIX_SECTION}" "${DISCUSS_SECTION}" "${SKIPPED_SECTION}"; do
     [ -z "${section}" ] && continue
     if [ -n "${SECTION_CONTENT}" ]; then
       SECTION_CONTENT="${SECTION_CONTENT}"$'\n\n'
@@ -360,7 +359,7 @@ else
     printf 'Original PR: https://github.com/%s/pull/%s\n' "${REPO}" "${PR_NUMBER}"
   } > "${issue_body_file}"
 
-  gh issue create --repo "${REPO}" --title "Follow-up: Review feedback from PR #${PR_NUMBER}" --body-file "${issue_body_file}"
+  FOLLOW_UP_URL=$(gh issue create --repo "${REPO}" --title "Follow-up: Review feedback from PR #${PR_NUMBER}" --body-file "${issue_body_file}")
 fi
 ```
 
@@ -373,6 +372,7 @@ Rules for follow-up issues:
 - Include the original reviewer username and comment link for each item
 - Include enough context that someone can act on the issue without re-reading the full PR review
 - After creating the issue, reference it in thread replies (e.g., "Tracked in #NNN for follow-up")
+- Capture the `gh issue create` output into `FOLLOW_UP_URL` (as shown above) so Step 10's summary comment can include the link
 - Return the issue URL to the user
 
 ## Step 10: Post PR Summary Comment

prompts/address-review.md

@@ -47,7 +47,7 @@ Execution flow when terminal access is available:
      - PR URL plus `check all reviews`
      - Specific review URL with `#pullrequestreview-...`
      - Specific issue comment URL with `#issuecomment-...`
-   - Detect the exact phrase `check all reviews`, set a `CHECK_ALL_REVIEWS` flag, and remove only that phrase before parsing the PR reference.
+   - Detect the phrase `check all reviews` (case-insensitive, trailing position only — must be the final tokens after the PR reference), set a `CHECK_ALL_REVIEWS` flag, and remove only that phrase before parsing the PR reference. If the phrase appears in any other position, do not treat it as an override; warn me and ask me to retry with the trailing form.
    - If the input is a full GitHub URL, extract the URL's `org/repo` before running `gh repo view`.
    - Extract the PR number and optional review/comment ID.
 
@@ -62,7 +62,7 @@ Execution flow when terminal access is available:
    - If `CHECK_ALL_REVIEWS` is true, ignore the cutoff and scan the full PR history.
    - If the input is a specific review URL or specific issue-comment URL, fetch that exact target even if it predates the latest summary comment.
    - Fetch the latest summary comment before collecting review data. Use a null-safe extraction so an empty result becomes an empty string (not JSON `null`):
-     `REVIEW_CUTOFF_AT=$(gh api --paginate repos/${REPO}/issues/{PR_NUMBER}/comments | jq -rs '[.[].[] | select(((.body // "") | contains("<!-- address-review-summary -->"))) | {id: .id, created_at: .created_at, html_url: .html_url}] | sort_by(.created_at) | last | if . == null then "" else .created_at end')`
+     `REVIEW_CUTOFF_AT=$(gh api --paginate repos/${REPO}/issues/{PR_NUMBER}/comments | jq -rs '[.[].[] | select((.body // "") | contains("<!-- address-review-summary -->")) | {id: .id, created_at: .created_at, html_url: .html_url}] | sort_by(.created_at) | last | if . == null then "" else .created_at end')`
    - An empty `REVIEW_CUTOFF_AT` means no prior summary comment; scan full history.
    - If `REVIEW_CUTOFF_AT` is non-empty and `CHECK_ALL_REVIEWS` is false, use it as the cutoff.
    - Use exact timestamps in user-facing status updates, for example `2026-04-01T20:14:33Z`.