bnadlerjr/dotfiles/managing-linear

Claude Code and agent skill by bnadlerjr/dotfiles

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Manages Linear issues via CLI using linearis (czottmann/linearis). Use when the user mentions Linear issue identifiers (e.g., 'ENG-123'), teams, cycles, projects, labels, issue management, or workflow automation. Handles issue CRUD, comments, cycle/project/label/team/user listing, document management, file embeds, search, and GitHub/GitLab PR linking via issue identifiers.

Install

npx vskill@latest install bnadlerjr/dotfiles/managing-linear

SKILL.md

Managing Linear

CLI-based Linear operations using linearis (czottmann/linearis).

Quick Start

Verify authentication before any operation:

bash
npx -y linearis teams list

If this fails, inform the user to set up authentication:

  1. Get a Personal API key from Linear: Settings > "Security & Access" > "Personal API keys"
  2. Save the token to ~/.linear_api_token, or export LINEAR_API_TOKEN=<token>

Workflow Patterns

Start Work on Issue
bash
# Read the issue
npx -y linearis issues read ENG-123
# Update status to In Progress
npx -y linearis issues update ENG-123 --status "In Progress"
Complete Issue
bash
# Move to done and add a comment
npx -y linearis issues update ENG-123 --status "Done"
npx -y linearis comments create ENG-123 --body "Completed in PR #456"
Daily Standup
bash
# My in-progress issues
npx -y linearis issues search "" --team "Engineering" | jq '[.[] | select(.status.name == "In Progress")]'
# Current cycle issues
npx -y linearis cycles list --team "Engineering" --active
Link PR to Issue

Include the issue identifier (e.g., ENG-123) in your Git branch name, PR title, or PR description. Linear's GitHub/GitLab integration automatically links PRs to issues when it detects the identifier.

Error Handling

bash
# Check if issue exists
if ! npx -y linearis issues read ENG-123 >/dev/null 2>&1; then
echo "Issue not found"
fi
# Check available teams before scoping
npx -y linearis teams list | jq '.[].name'
# Check available labels before assigning
npx -y linearis labels list --team "Engineering" | jq '.[].name'

Best Practices

  1. All output is JSON - pipe to jq for parsing and filtering
  2. Use smart ID resolution - linearis accepts both IDs and human-readable names for teams, projects, and cycles
  3. Priority scale is inverted - 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
  4. Use label management modes - --label-by adding (default), replacing, or removing to control label behavior
  5. Scope searches with --team and --project for faster, more relevant results
  6. Write multi-line content to /tmp first when creating documents or descriptions with complex markdown

References

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/bnadlerjr/dotfiles/managing-linear/badge)](https://verified-skill.com/skills/bnadlerjr/dotfiles/managing-linear)

Something wrong with this skill or its page? Tell us.