sudocode feedback show

Syntax

sudocode feedback show <feedback-id>

Description

The feedback show command displays comprehensive details about a feedback entry, including:

Feedback ID and type
Source issue and target spec
Dismissed status and agent
Creation and update timestamps
Full feedback content
Anchor location with status
Original location (if relocated or stale)
Context snippets

Use this to review feedback in detail before addressing it or to understand the context of a specific comment, suggestion, or request.

This command shows the complete feedback content, unlike feedback list which only shows a preview.

Arguments

feedback-id

string

required

The feedback ID to displayExample: FB-001The unique identifier for the feedback entry.

Examples

Show Basic Feedback

Display feedback details:

sudocode feedback show FB-001

Expected output

FB-001 request
────────────────────────────────────────────────────────────
Issue: ISSUE-001
Spec: SPEC-001
Status: Active
Agent: alice
Created: 2025-10-29T10:15:00Z
Updated: 2025-10-29T10:15:00Z

Content:
Token expiration policy not specified. Should we use fixed or sliding window?
Consider adding explicit policy in the Authentication section with recommended
values for access tokens (15 minutes) and refresh tokens (7 days).

Anchor Location:
  Status: valid
  Section: Authentication Flow
  Line: 42
  Snippet: "Token expiration policy"

Show Feedback with Stale Anchor

View feedback with outdated anchor:

sudocode feedback show FB-004

Expected output

FB-004 request
────────────────────────────────────────────────────────────
Issue: ISSUE-015
Spec: SPEC-001
Status: Active
Agent: bob
Created: 2025-10-28T14:30:00Z
Updated: 2025-10-29T09:00:00Z

Content:
Need clarification on error response format. Should we use RFC 7807
problem details format or custom error structure? This affects client
error handling implementation.

Anchor Location:
  Status: stale
  Section: Error Handling
  Line: 45
  Snippet: "Error response format"

Original Location:
  Line: 38
  Section: Error Handling

When anchor status is “stale” or “relocated”, the original location is shown for reference.

Show Relocated Feedback

View feedback that was moved:

sudocode feedback show FB-005

Expected output

FB-005 suggestion
────────────────────────────────────────────────────────────
Issue: ISSUE-020
Spec: SPEC-003
Status: Active
Agent: carol
Created: 2025-10-27T11:00:00Z
Updated: 2025-10-29T10:45:00Z

Content:
Consider using enum type instead of string constants for user roles.
This provides better type safety and IDE autocomplete support.

Example:
enum UserRole {
  ADMIN = 'admin',
  USER = 'user',
  GUEST = 'guest'
}

Anchor Location:
  Status: relocated
  Section: Data Model
  Line: 92
  Snippet: "User role definitions"

Original Location:
  Line: 85
  Section: User Schema

Show Dismissed Feedback

View resolved feedback:

sudocode feedback show FB-003

Expected output

FB-003 suggestion
────────────────────────────────────────────────────────────
Issue: ISSUE-010
Spec: SPEC-002
Status: Dismissed
Agent: alice
Created: 2025-10-26T09:00:00Z
Updated: 2025-10-28T16:30:00Z

Content:
Consider adding rate limiting to prevent abuse: 10 requests/minute per client.
Could use token bucket algorithm with Redis for distributed tracking.

Anchor Location:
  Status: valid
  Section: API Endpoints
  Line: 78
  Snippet: "Rate limiting policy"

Show Comment Feedback

View implementation notes:

sudocode feedback show FB-002

Expected output

FB-002 comment
────────────────────────────────────────────────────────────
Issue: ISSUE-005
Spec: SPEC-001
Status: Active
Agent: bob
Created: 2025-10-29T11:00:00Z
Updated: 2025-10-29T11:00:00Z

Content:
OAuth flow implemented successfully with PKCE extension as specified.
Used authorization code flow with state parameter for CSRF protection.
Access token TTL set to 1 hour, refresh token to 30 days as per OAuth 2.0
best practices.

Anchor Location:
  Status: valid
  Section: OAuth 2.0 Flow
  Line: 30
  Snippet: "OAuth implementation details"

JSON Output

Get machine-readable output:

sudocode --json feedback show FB-001

JSON output

{
  "id": "FB-001",
  "issue_id": "ISSUE-001",
  "spec_id": "SPEC-001",
  "feedback_type": "request",
  "content": "Token expiration policy not specified. Should we use fixed or sliding window? Consider adding explicit policy in the Authentication section with recommended values for access tokens (15 minutes) and refresh tokens (7 days).",
  "agent": "alice",
  "anchor": {
    "line_number": 42,
    "section_heading": "Authentication Flow",
    "text_snippet": "Token expiration policy",
    "anchor_status": "valid",
    "context_before": "## Authentication Flow\n\nThe system uses JWT tokens for authentication.",
    "context_after": "Tokens should be validated on each request.\n\n### Token Refresh"
  },
  "dismissed": false,
  "created_at": "2025-10-29T10:15:00Z",
  "updated_at": "2025-10-29T10:15:00Z"
}

Understanding Feedback Details

Feedback Types

comment

Informational notesDocuments implementation decisions, shares learnings, or provides status updates. No action required.

suggestion

Improvement proposalsProposes changes or enhancements to the spec based on implementation experience.

request

Clarification neededPoints out ambiguities or missing requirements discovered during implementation.

Anchor Status

The anchor status indicates whether the feedback location is still accurate:

valid (green)

Anchor is accurate - the line number and context match the current spec content.No action needed.

relocated (yellow)

Content moved but anchor was successfully updated to new location.Review to confirm accuracy, but usually fine.

stale (red)

Content changed significantly - anchor may be invalid or pointing to wrong location.Action required: Use feedback relocate to manually fix the anchor.

Original Location

When feedback has been relocated or become stale, the “Original Location” section shows:

The line number where the anchor was originally created
The section heading at that original location

This helps you understand where the feedback was initially anchored and track how the spec has evolved.

Common Workflows

Review Feedback Before Responding

Show feedback details

sudocode feedback show FB-001

View spec context

sudocode spec show SPEC-001

Update spec if needed

Edit the spec to address the feedback

Dismiss feedback

sudocode feedback dismiss FB-001

Investigate Stale Feedback

Find stale feedback

sudocode feedback stale

Show details

sudocode feedback show FB-004

View current spec

sudocode spec show SPEC-001

Look at the original line number to see what changed

Relocate or dismiss

# If still relevant, relocate
sudocode feedback relocate FB-004 --line 50

# If no longer relevant, dismiss
sudocode feedback dismiss FB-004

Audit Implementation Feedback

View all feedback from a completed issue:

List issue feedback

sudocode feedback list --issue ISSUE-005

Review each entry

sudocode feedback show FB-002

Extract learnings

Use feedback to improve future specs

Generate Feedback Report

Create a summary of feedback:

# Show all active requests
for fb_id in $(sudocode --json feedback list --type request --dismissed false | jq -r '.[] | .id'); do
  echo "=== $fb_id ==="
  sudocode feedback show "$fb_id"
  echo
done

Scripting Examples

Extract Feedback Content

# Get just the content text
sudocode --json feedback show FB-001 | jq -r '.content'

Check Anchor Status

# Get anchor status for a feedback
status=$(sudocode --json feedback show FB-001 | jq -r '.anchor.anchor_status')
echo "Anchor status: $status"

Find Feedback Location

# Get spec and line number
sudocode --json feedback show FB-001 | jq -r '"\(.spec_id):\(.anchor.line_number)"'
# Output: SPEC-001:42

Batch Review

# Review all feedback for a spec
for fb_id in $(sudocode --json feedback list --spec SPEC-001 | jq -r '.[] | .id'); do
  echo "Reviewing $fb_id..."
  sudocode feedback show "$fb_id"
  echo "Press enter for next..."
  read
done

Common Questions

How do I see the feedback in context of the spec?

Use spec show to view the spec with all its feedback:

sudocode spec show SPEC-001

This shows feedback anchored to specific locations in the spec content.

What does the snippet show?

The snippet is a short excerpt from the spec at the anchor location. It helps confirm the feedback is pointing to the right content.

Can I edit feedback after creating it?

No, there’s no edit command. To modify feedback:

Dismiss the old feedback
Add new feedback with updated content

Why does dismissed feedback show old timestamps?

updated_at reflects when the feedback was last modified, including when it was dismissed. The dismiss action updates this timestamp.

What's the difference between context_before and context_after?

These are lines surrounding the anchor point:

context_before - Text above the anchor location
context_after - Text below the anchor location

They help verify the anchor is still pointing to the correct location.

Can I show multiple feedback entries at once?

Not with a single command. Use shell scripting:

for id in FB-001 FB-002 FB-003; do
  sudocode feedback show "$id"
done

Troubleshooting

Error: Feedback not found

Cause: The feedback ID doesn’t existSolution: List all feedback to find the correct ID:

sudocode feedback list

Anchor shows as stale but content looks correct

Cause: Line numbers changed due to edits elsewhere in specSolution: If the location is still correct, update status to relocated:

sudocode feedback relocate FB-001 --line 42

Original location is missing

Cause: Feedback has never been relocated (status is valid)Solution: Original location only appears when status is “relocated” or “stale”. Valid anchors don’t need it.

Content is truncated in JSON output

Cause: Content is likely complete, check if it’s a display issueSolution: Verify content length:

sudocode --json feedback show FB-001 | jq -r '.content | length'

feedback list

List all feedback

feedback add

Add new feedback

feedback dismiss

Dismiss feedback

feedback relocate

Relocate stale anchor

spec show

View spec with feedback

issue show

View issue with feedback

Next Steps

List feedback

sudocode feedback list --dismissed false

Show details

sudocode feedback show FB-001

Review spec

sudocode spec show SPEC-001

Take action

Update spec, relocate anchor, or dismiss feedback

Feedback System Concept Guide

Learn more about the feedback system and bidirectional learning

CLI Reference

Spec Commands

Issue Commands

Relationship Commands

Feedback Commands

Query & Sync Commands

​Syntax

​Description

​Arguments

​Examples

​Show Basic Feedback

​Show Feedback with Stale Anchor

​Show Relocated Feedback

​Show Dismissed Feedback

​Show Comment Feedback

​JSON Output

​Understanding Feedback Details

​Feedback Types

comment

suggestion

request

​Anchor Status

​Original Location

​Common Workflows

​Review Feedback Before Responding

​Investigate Stale Feedback

​Audit Implementation Feedback

​Generate Feedback Report

​Scripting Examples

​Extract Feedback Content

​Check Anchor Status

​Find Feedback Location

​Batch Review

​Common Questions

​Troubleshooting

​Related Commands

feedback list

feedback add

feedback dismiss

feedback relocate

spec show

issue show

​Next Steps

Feedback System Concept Guide

Syntax

Description

Arguments

Examples

Show Basic Feedback

Show Feedback with Stale Anchor

Show Relocated Feedback

Show Dismissed Feedback

Show Comment Feedback

JSON Output

Understanding Feedback Details

Feedback Types

Anchor Status

Original Location

Common Workflows

Review Feedback Before Responding

Investigate Stale Feedback

Audit Implementation Feedback

Generate Feedback Report

Scripting Examples

Extract Feedback Content

Check Anchor Status

Find Feedback Location

Batch Review

Common Questions

Troubleshooting

Related Commands

Next Steps