Slamb2k Devsolo
- 1 repo stars
- Updated October 21, 2025
- slamb2k/devsolo
slamb2k-devsolo is a Claude Code plugin that connects DevSolo git MCP automation for linear history, branches, and PR workflows.
About
slamb2k-devsolo is a Claude Code plugin built around DevSolo, described as a git workflow automation tool that enforces linear history and helps prevent merge conflicts. The catalog lists developer-tools positioning, MCP server tooling, and keywords such as branch-management, pr-automation, and ci-integration. developers shipping from feature branches use it when agents should rebase, open PRs, or keep history linear instead of piling merge commits. Canonical placement is Ship review because the value shows up at merge time, but daily Build work benefits too—treat journey scope as multi-phase across build commits and ship gates. The bundle contains one plugin, so expectations stay focused: this is git and PR mechanics, not hosting or observability. Register it when you already use Claude Code with MCP and want agent actions to follow a strict git policy your team defined in DevSolo.
- Git workflow automation with linear history enforcement
- Branch management and PR automation via MCP server tools
- Aimed at preventing merge conflicts before they reach main
- CI-integration and developer-focused workflow keywords in catalog
- Single-plugin bundle from slamb2k/devsolo repository
Slamb2k Devsolo by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install slamb2k-devsolo@slamb2k/devsoloAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | October 21, 2025 |
| Repository | slamb2k/devsolo ↗ |
What it does
Install when you want Claude to drive DevSolo’s git MCP workflow for linear history, branch management, and PR automation without merge-conflict churn.
Who is it for?
Best when you want agent-driven git hygiene and PR automation aligned with linear-history rules.
Skip if: Skip if you're on heavy merge-commit workflows that forbid rebases or anyone not running Claude Code with MCP git tooling.
What you get
After install, Claude Code can use DevSolo MCP tools to manage branches and PRs while keeping linear history and fewer conflict-prone merges.
- Agent-executable git branch and PR operations via MCP
- Cleaner linear history on main integration branches
- Reduced manual steps before review and merge
By the numbers
- 1 plugin in the bundle
- Repository slamb2k/devsolo
- Catalog category developer-tools with MCP and PR-automation keywords
Recommended Plugins
Ahmedasmar Devops Claude SkillsA Claude Code Skills Marketplace for DevOps workflows189
Akin Ozer Cc Devops SkillsA practical skill pack for DevOps work in Claude Code and Codex.281
Antonbabenko Terraform SkillThe Claude Agent Skill for Terraform and OpenTofu - testing, modules, CI/CD, and production patterns2.2k
Aws Samples Aws Emr Utilities1 plugin45
Awudevelop Claude PluginsProduction-ready Claude Code plugins for workflow automation and productivity
Axiomhq CliThe power of Axiom on the command line.59How it compares
Git and PR MCP automation plugin, not a CI host replacement or code-review skill pack.
FAQ
Who is Slamb2k Devsolo for?
It is for developers using Claude Code who want DevSolo’s MCP-driven git automation to enforce linear history and streamline pull requests.
When should I use Slamb2k Devsolo?
Use it during Ship review when merging features and whenever you want agents to manage branches and PRs without creating conflict-prone git states.
How do I add Slamb2k Devsolo to my agent?
Install the slamb2k/devsolo Claude Code plugin, configure the DevSolo MCP server per the repo README, and grant git remote access in your local or CI environment.