Claude Code statusline that checks the active pull request body for GitHub closing keywords and shows whether issue auto-closure linkage is present.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
3 safety and 3 privacy notes across 2 risk areas. Review closely: network access.
#!/usr/bin/env bash
set -u
main() {
if ! command -v gh >/dev/null 2>&1; then
echo "linkage: gh missing"
exit 0
fi
if ! command -v jq >/dev/null 2>&1; then
echo "linkage: jq missing"
exit 0
fi
pr_json=$(gh pr view --json number,body 2>/dev/null || true)
if [ -z "$pr_json" ]; then
echo "linkage: no active PR"
exit 0
fi
number=$(printf '%s' "$pr_json" | jq -r '.number // empty')
body=$(printf '%s' "$pr_json" | jq -r '.body // ""')
closing_refs=$(printf '%s\n' "$body" | grep -Eio '\b(close[sd]?|fix(e[sd])?|resolve[sd]?)[: ]+#([0-9]+)' | wc -l | tr -d ' ')
if [ "$closing_refs" -gt 0 ]; then
state="linked"
else
state="missing close"
fi
printf 'linkage: PR #%s | closing refs %s | %s\n' "$number" "$closing_refs" "$state"
}
case $- in
*n*) ;;
*) main "$@" ;;
esac{
"statusLine": {
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/pr-closing-keywords-statusline.sh"
}
}Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for pr-closing-keywords-statusline, PR issue linkage, closing keywords, GitHub pull request linkage, and gh-pr-issue-linkage-statusline. The earlier cli.github.com submission was self-closed after #960 showed that source domain overlaps the accepted repository-health statusline; this replacement uses GitHub's issue-linking documentation and a closing-keyword-focused scope.
Editorial statusline recipe. No paid placement or affiliate link is used.
Show that PR Closing Keywords Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/statuslines/pr-closing-keywords-statusline)PR Closing Keywords Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Claude Code statusline that checks the active pull request body for GitHub closing keywords and shows whether issue auto-closure linkage is present. Open dossier | Claude Code statusline that reads GitHub REST check runs for the active pull request head commit and summarizes failed, pending, and passing checks. Open dossier | Claude Code statusline that counts GitHub Flavored Markdown task list items from a linked issue body or local issue-body file. Open dossier | Claude Code statusline that uses GitHub CLI to show repository health basics: archive state, open PR count, open issue count, and default branch. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | MkDev11 | MkDev11 | MkDev11 | MkDev11 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | |||
| Category | statuslines | statuslines | statuslines | statuslines |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | MkDev11 | MkDev11 | MkDev11 | MkDev11 |
| Added | 2026-06-04 | 2026-06-04 | 2026-06-04 | 2026-06-04 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Closing keywords are workflow signals, not proof that the PR actually satisfies the linked issue. Some repositories use manual issue closure or external trackers, so missing keywords should be interpreted with project policy. Keep automated PR body edits separate from this read-only statusline. | ✓Check-run counts are a review prompt, not proof that every required branch protection rule is satisfied. Repositories with more than 100 check runs may need pagination or a slower dedicated dashboard. Keep the refresh interval moderate so the statusline does not repeatedly query GitHub APIs. | ✓Task completion is a planning signal and should not replace tests, review, or acceptance criteria. Branch-derived issue numbers are a convenience; set GITHUB_ISSUE_NUMBER explicitly when branch names contain unrelated numbers. Keep issue bodies free of secrets before using them in terminal-visible automation. | ✓Repository counts are orientation signals and should not replace issue triage, release gates, or maintainer review. The `--limit 100` query cap keeps the statusline fast; very large queues may need a dedicated dashboard. The script does not modify repository settings, issues, or pull requests. |
| Privacy notes | ✓The script prints only aggregate closing-reference counts and the pull request number. It reads the pull request body, which can contain private planning details in private repositories. Private repository access follows the local GitHub CLI account and organization policy. | ✓The script prints aggregate check-run counts and the pull request number. Private repository metadata follows the local GitHub CLI account and may appear in terminal recordings. The statusline does not print check names, workflow names, branch names, or commit messages. | ✓The statusline prints only aggregate task counts and an issue number or local label. If GitHub CLI fetches private issue bodies, access follows the local account and organization policy. Local issue-body files can contain sensitive planning details; avoid echoing raw bodies in shared logs. | ✓The statusline prints repository owner/name, counts, default branch, and state. Private repository metadata follows the local GitHub CLI login and may appear in terminal screenshots. Organization policies can restrict which counts are visible to the local account. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Use focused Claude subagents for PR review and issue triage.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.