Skip to main content

Syntax

tracer dep cycles

Options

--json
boolean
Output result in JSON format

Examples

# Check for dependency cycles
tracer dep cycles

Output

Human-Readable Format (No Cycles)

✓ No dependency cycles detected

Human-Readable Format (Cycles Found)

⚠ Found 2 cycle(s):

Cycle 1:
  → bd-2 Design auth schema
  → bd-5 Implement OAuth
  → bd-2 Design auth schema

Cycle 2:
  → bd-10 Create API
  → bd-11 Write docs
  → bd-12 Deploy service
  → bd-10 Create API

JSON Format (No Cycles)

[]

JSON Format (Cycles Found)

[
  [
    {
      "id": "bd-2",
      "title": "Design auth schema",
      "status": "in_progress",
      "priority": 1,
      "issue_type": "task",
      "assignee": "[email protected]",
      "created_at": "2025-03-04T10:00:00Z",
      "updated_at": "2025-03-04T11:00:00Z"
    },
    {
      "id": "bd-5",
      "title": "Implement OAuth",
      "status": "open",
      "priority": 1,
      "issue_type": "task",
      "assignee": "",
      "created_at": "2025-03-04T10:05:00Z",
      "updated_at": "2025-03-04T10:05:00Z"
    },
    {
      "id": "bd-2",
      "title": "Design auth schema",
      "status": "in_progress",
      "priority": 1,
      "issue_type": "task",
      "assignee": "[email protected]",
      "created_at": "2025-03-04T10:00:00Z",
      "updated_at": "2025-03-04T11:00:00Z"
    }
  ]
]
Circular dependencies indicate a logical error in your dependency graph. Issues in a cycle cannot be completed because they each depend on the other.
Use tracer dep remove <from> <to> to break cycles by removing incorrect dependencies.

Build docs developers (and LLMs) love