shipper issue view

shipper issue view

Usage: shipper issue view [options]

Show full issue detail, including current or historical required-check failures

Arguments

Argument	Required	Description	Choices
	yes	Shipper issue ID, gh:, or GitHub URL	-

Flags

Long	Short	Value	Default	Description	Choices
—json	-	-	false	output the issue detail as JSON	-
—review-round	-		-	show full content for one retained review round	-

Examples

Show the complete locally retained detail for a Shipper issue.

shipper issue view S#42

Emit one machine-readable issue detail document by GitHub reference.

shipper issue view gh:1377 --json

Show the complete content of one locally retained review round.

shipper issue view S#42 --review-round round-2

Required-check failures

New automatic check stops apply only to independently acquired hosted checks. Hosted-check external obstruction and unchanged-revision stalled remediation enter Failed over Rework while retaining useful fixes, package/branch/PR identity, answers, evidence and delivery debt. Obstruction requires concrete evidence, cause, external remedy and final-HEAD applicability after same-pass fixes; red status, main-branch match or missing tools alone are insufficient. The mechanical backstop requires a completed current V4 check-only review with retained answers and identical fresh failures on unchanged HEAD after refresh/rerun/flake opportunities. Nits are neutral; changed/passed/new/material/pending/unavailable evidence and request-changes bodies veto it. Sandbox limitations remain ordinary investigation. A skipped review consumes no allowance and each stop counts once toward terminal safety. No report, answer, resolution or retry waives required checks or permits red ship/merge. Remedy/restart alone stays Failed. Preserving shipper reset S#123 --to rework and eligible shipper recover S#123 renew allowance on unchanged HEAD, preserve unpublished work and history, and require fresh normal verification. Existing eligibility, locks, closure holds and confirmation rules apply. Missing/divergent retained refs refuse retry. Read current or historical diagnosis, local procedures and pending delivery with issue view/get-issue, including roundless failures. Local verification uses existing prose summaries and relevant comments, without a structured local evidence report. Every attempted non-permission local failure, including apparently unrelated or pre-existing failures, requires an anchored 🔴 must-fix: comment on the most relevant changed line and REQUEST_CHANGES, then ordinary Rework fixes or prose replies. Permission-denied and unattempted checks are limitations, never passes or waivers; all previously required checks stay required. Local-only workflows have no local-evidence automatic stop; the ordinary review-round cap still applies. Historical local observations and failure records remain readable without migration. Outstanding historical local findings receive ordinary prose replies and never authorize a new automatic stop. Upgrade alone does not clear findings, renew allowance, or recover Failed. Publication and hook diagnostics and required hook execution remain unchanged.

Exit Codes

Code	When
0	The issue detail renders successfully, including when linked pull request state is unavailable.
1	Startup, license, repository linkage, reference resolution, or local store access fails.

Constraints

• Design, Plan, Implement, Review, Rework, and Ready name next work. Designed simple issues next Implement; complex or undecided issues next Plan. Packaged work next Review in either PR mode. Ready means ready for final integration, not shipped. New stays separate; held and failed are excluded (hold wins), while blocked, locked, paused, and running retain membership. CLI/MCP retain six next-step groups; desktop has five columns, with Implement combining Implement and Rework for the same population and attention exclusions. Current nextStep and nextStepPipeline are additive; completed-stage pipeline fields, labels, filters, commands, reset arguments, and historical records retain their meanings. Maintained label descriptions automatically refresh during next normal setup or maintenance, without separate initialization; successful cache skips repeats and force refresh reads again. Read-only status makes no label writes.
• The command is read-only and offers no title, body, priority, or workflow-state editing capability.
• Issue title, body, lifecycle metadata, closure data, and workflow history come only from the local issue-state store; the command never fetches issue content from GitHub.
• The body section is absent when the exact retained body is empty, and the history section is absent when no live Shipper workflow entries remain.
• The Lifecycle section shows the current route when it is simple or complex and omits the row when the route is undecided, using the same presentation rule as the issue listing marker. --json always emits lifecycle.route, like every other lifecycle field.
• GitHub-sourced inline PR review threads are not shown here; locally retained Shipper review rounds are shown under Reviews.
• The default compact Reviews list includes every retained review round oldest first with its number, stable identity, reviewed revision, disposition, finding count, optional addressed/superseded handling state, and optional pull request reference. A round with no handling history remains fully readable without handling markers.
• --review-round <round-id> selects one exact stable identity and adds its unbounded full content: overall feedback, complete stable finding identities and diff locations/ranges, comment and reply text, optional handling markers, and complete partial coverage with explicit None when empty.
• Human output omits Reviews when no rounds exist, while --json always includes typed available-empty Reviews. An unreadable review record renders a distinct Reviews error and reason without hiding the rest of the issue.
• Retained Reviews remain available on completed and not-planned closed records; browsing never changes the review record or handling state.
• External GitHub comments are not displayed; superseded workflow entries are replaced and retracted notes leave no marker.
• Closed records show only their retained identity, title, optional body, recorded closure outcome, last stage, closure time, optional history, and locally retained Reviews. Live-only metadata and the issue-level linked pull request section are absent.
• A linked pull request section is absent when no pull request is recorded. With effective transport origin, live state lookup is attempted once, is never retried, and terminates after two seconds.
• When Reviews is non-empty or unavailable, review and issue content renders fully from local state and no pull request state lookup is attempted. Available-empty Reviews retains the existing origin-backed two-second pull request enrichment.
• With effective transport none, the stored pull request number remains visible in human and JSON output, state is omitted, and no remote lookup is attempted. Under origin with available-empty Reviews, lookup failure or timeout leaves the reference visible, omits its human-readable state, records an unavailable reason in JSON, and still exits successfully.
• --json writes exactly one pretty-printed document and distinguishes no recorded pull request, a known state, and an unavailable state.