alienfast/deps
skills/deps/SKILL.md
Visualize and analyze issue dependencies in Linear. Finds blocking chains, circular dependencies, and critical path items.
testing
Updated Apr 15, 2026
$ install --global
skillsauthnpx skillsauth add alienfast/claude depsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 6:08 PM4.6s1 file scanned
SKILL.md
- name:
- deps
- description:
- Visualize and analyze issue dependencies in Linear. Finds blocking chains, circular dependencies, and critical path items.
Deps Skill - Dependency Analysis
You are an expert at analyzing and visualizing software project dependencies.
When to Use
Use this skill when:
- Understanding what's blocking an issue
- Planning work order
- Identifying circular dependencies
- Finding critical path items
Process
-
Visualize Dependencies
linear deps ENG-100 linear deps --team ENG -
Analyze Blocking Chains
- Find longest blocking chains
- Identify bottleneck issues
- Locate circular dependencies
-
Recommend Actions
Dependency Types
| Type | Meaning | Example | |------|---------|---------| | blocks | A must complete before B | Auth blocks Login UI | | blocked_by | B cannot start until A done | Login UI blocked by Auth | | related | Informational link | Two related features | | duplicate | Same issue | Close one, reference other |
Visualization Output
DEPENDENCY GRAPH: ENG-100
════════════════════════════════════════
ENG-100 User Authentication Epic
├─ ENG-101 Login flow [In Progress]
│ ├─ ENG-103 OAuth integration [Todo]
│ │ → blocks: ENG-105
│ └─ ENG-104 Session management [Todo]
├─ ENG-102 Logout flow [Blocked]
│ ← blocked by: ENG-101
└─ ENG-105 Token refresh [Blocked]
← blocked by: ENG-103
────────────────────────────────────────
5 issues, 4 dependencies, 0 cycles
Analysis Areas
Blocking Chains
Issues that block many other issues are critical:
Critical blocker: ENG-101
→ blocks 3 issues directly
→ blocks 5 issues transitively
Circular Dependencies
Cycles prevent any issue from completing:
⚠ Circular dependency detected:
ENG-201 → ENG-202 → ENG-203 → ENG-201
Critical Path
Longest dependency chain determines minimum completion time:
Critical path (4 issues):
ENG-100 → ENG-101 → ENG-103 → ENG-105
Minimum time: 4 issue completion times
Orphaned Dependencies
Issues referencing non-existent or closed issues:
⚠ Orphaned dependencies:
ENG-150 blocked by ENG-099 (closed)
Commands Used
# Single issue dependencies
linear deps ENG-100
# Team-wide dependencies
linear deps --team ENG
# Check what blocks an issue
linear issues blocked-by ENG-100
# Check what an issue blocks
linear issues blocking ENG-100
# Create a dependency
linear issues update ENG-102 --blocked-by ENG-101
# Remove a dependency (update with empty)
linear issues update ENG-102 --blocked-by ""
Discovery Commands (NEW)
Use search to discover dependency-related issues:
# Find all blocked issues (useful for prioritizing unblocking work)
linear search --has-blockers --team ENG
# Find issues blocked by a specific issue
linear search --blocked-by ENG-100
# Find issues blocking a specific issue
linear search --blocks ENG-100
# Find circular dependencies
linear search --has-circular-deps --team ENG
# Find complex dependency chains
linear search --max-depth 5 --team ENG
Pro tip: Use /link-deps skill to discover and establish missing dependencies across your backlog.
Action Recommendations
Based on analysis, recommend:
- Unblock critical path - Prioritize blockers
- Break cycles - Remove unnecessary dependencies
- Parallelize - Find work that can happen concurrently
- Update stale deps - Clean up outdated relationships
Best Practices
- Keep dependencies minimal - Only add necessary ones
- Use blocks, not blocked_by - Clearer mental model
- Review regularly - Dependencies become stale
- Document non-obvious deps - Add comments explaining why
Related Skills
alienfast/reap-worktrees
data-ai
VerifiedTrustedCommunity
Inspect and reclaim leftover /start wt worktrees. Shows which worktrees under .claude/worktrees/ are eligible for cleanup (PR merged, branch merged, or Linear issue Canceled/Done) and which are preserved (active or abandoned-for-resumption), and can reap the eligible ones now. Use when the user says 'reap worktrees', 'clean up worktrees', 'what worktrees are leftover', 'prune worktrees', or invokes /reap-worktrees.
SKILL.mdUpdated Jun 12, 2026
alienfast/merge-queue
testing
VerifiedTrustedCommunity
Inspect and drain the local deferred-merge queue. Shows worktree merges that /finish deferred (transient block — e.g. the main checkout was on the source branch with WIP) and that a local launchd drainer retries until they land. Use when the user says 'merge queue', 'what merges are pending', 'drain the merge queue', or invokes /merge-queue.
SKILL.mdUpdated Jun 11, 2026
alienfast/full
testing
VerifiedTrustedCommunity
End-to-end Linear issue macro — runs /start then /finish in sequence, gated on the /quality-review verdict. Worktree mode is opt-in via the `wt` token, mirroring /start. Pauses only for plan approval and the deferred-items filing decision; otherwise autonomous. Use when the user says 'full PL-XX', 'ship PL-XX end-to-end', or invokes /full.
SKILL.mdUpdated May 28, 2026
alienfast/quality-review
development
VerifiedTrustedCommunity
Adversarial implementation review with triage and fix loop. Hard-gates on `pnpm check`, delegates to the quality-reviewer agent for categorized findings (Critical/High/Medium/Nice-to-Have/Approved), then triages and fixes findings via the developer agent. Loops until a re-review surfaces no new Critical/High/Medium findings (convergence), with a soft ceiling of 5 cycles before asking the user how to proceed; option 3 of that prompt terminates with verdict `escalated-to-architect`. Use when the user says 'review my work', 'check this implementation', 'adversarial review', 'quality review', or invokes /quality-review.
SKILL.mdUpdated Apr 29, 2026