By bahamoth
Linear issue-tracked development workflow for Claude Code. Enforces branch naming, commit conventions, and Linear issue tracking.
npx claudepluginhub bahamoth/claude-linear-workflow --plugin linear-workflowA Claude Code plugin that enforces Linear issue-tracked development workflow with branch naming conventions, Conventional Commits validation, and automatic issue tracking.
# 1. Add marketplace
/plugin marketplace add bahamoth/claude-marketplace
# Or host your own marketplace - see https://code.claude.com/docs/en/plugin-marketplaces
# 2. Install plugin
/plugin install linear-workflow@bahamoth/claude-marketplace
# 3. Enable plugin
/plugin enable linear-workflow
# 4. Authenticate Linear MCP (opens browser for OAuth)
/mcp linear-mcp auth
Add your Linear team to .claude/settings.json:
{
"env": {
"LINEAR_WORKFLOW_TEAM": "YourTeam",
"LINEAR_WORKFLOW_PROJECT": "YourProject"
}
}
| Variable | Required | Description |
|---|---|---|
LINEAR_WORKFLOW_TEAM | Yes | Your Linear team name |
LINEAR_WORKFLOW_PROJECT | No | Project for new issues (Backlog if omitted) |
If LINEAR_WORKFLOW_TEAM is not configured, the plugin will block implementation and guide you to set it up.
Has Issue No Issue
│ │
▼ ▼
Query via MCP Plan → Create Issue in Linear
│ │
└──────────┬─────────────────┘
▼
Create branch (use gitBranchName)
▼
Linear status: In Progress + start comment
▼
Work (comment on decisions/blockers)
▼
Create PR (Fixes {PREFIX}-XX)
▼
Merge (rebase-ff) → Linear auto-Done
When you try to exit plan mode on main, the plugin blocks and guides you to:
gitBranchNameUse the gitBranchName field from the Linear issue:
git checkout -b <gitBranchName>
Branch format is configured in Linear: Settings > Workspace > Integrations > Branch format
Follow Conventional Commits format:
type(scope): description
Refs ABC-123
Format: type(scope): description where type is any lowercase word (commonly feat, fix, docs, refactor, etc.)
Include Linear magic words to auto-close issues:
Fixes ABC-123
| Hook | Event | Matcher | Purpose |
|---|---|---|---|
check_linear_env.py | UserPromptSubmit | - | Early warning if env not configured |
check_linear_env.py | PreToolUse | Write|Edit|ExitPlanMode | Re-check env before implementation |
ensure_linear_branch.py | PreToolUse | Write|Edit|ExitPlanMode | Enforce Linear branch before changes |
validate_commit_msg.py | PreToolUse | Bash | Validate Conventional Commits |
| Prompt | PreCompact | - | Sync progress to Linear comments |
MIT
Battle-tested Claude Code plugin for engineering teams — 38 agents, 156 skills, 72 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
External network access
Connects to servers outside your machine
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques