Clarify stack PR URL reporting

Author: RhysSullivan

.agents/skills/stack/SKILL.md

@@ -79,6 +79,10 @@ Use this to understand local stack metadata, current branch position, missing
 parents, tracked PR numbers, and PR titles when GitHub is available. It is
 opinionated: backup branches are hidden, and when the current branch is
 stack-relevant it focuses on that stack instead of listing every local branch.
+When relaying a stack view to the user, always include the full PR URLs for
+every branch that has a PR, not just PR numbers or titles. If `stack status`
+does not print a URL for a branch, query GitHub with `gh pr view`/`gh pr list`
+and include the URL in the shown stack view.
 
 Use `stack sync --dry-run`, not `stack status`, when you need GitHub PR-base
 inference before mutation.
@@ -129,6 +133,8 @@ nonzero if any stack failed.
 Sync output is intentionally outcome-oriented. It should show the stack tree with
 icons like `●`, `✓`, `◌`, and `✕`, plus changed PRs/backups/undo instructions. It
 should not default to internal phase logs like fetch, inspect, or reconcile.
+When you show a stack tree to the user, include full PR URLs alongside each PR
+entry so the stack view is directly actionable.
 
 If a replay fails, `stack sync` aborts the failed cherry-pick, restores the
 original branch, deletes the temporary replay branch, keeps backups and the undo