from linear-cli116
Automatically discover likely dependency relationships between backlog issues and suggest/block links to establish correct work order.
Link Deps scans issue text and backlog lists to find candidate dependency relationships (what blocks what) and produces actionable recommendations to link issues as blockers/blocked. It provides search-and-verify commands and patterns to identify foundation work, feature work, and circular dependencies, plus concrete commands to update issue trackers.
Use this skill when your backlog is large or unstructured and you need to: identify prerequisite work, break cycles, prioritize foundation tasks, or prepare a sprint with clear work order. Run it during backlog grooming, pre-planning sessions, or after large refactors/migrations.
--blocked-by, and verify the dependency graph).This is best used in agents that can run or suggest CLI commands and parse issue-tracker outputs (e.g., agents integrated with developer tooling or CLIs like Linear).
A Linear CLI skill for discovering and linking issue dependencies in backlogs. No bundled scripts — purely instructional SKILL.md with CLI command examples. Well-structured discovery patterns and workflow examples, but relies entirely on the `linear` CLI being installed and configured. No programmatic output contracts or automation beyond manual CLI commands.
Pure documentation skill with no scripts. Security is clean — no shell injection risks, no network calls beyond the Linear CLI itself. Architecture is basic: single SKILL.md with no scripts/, references/, or separation of concerns. Frontmatter minimal (name + description only). Code quality is decent: clear patterns, good examples, but missing error handling guidance and no idempotent automation. Usefulness is moderate: solves a real problem for Linear users but niche audience and requires heavy manual CLI work.
