Slamb2k Devsolo
slamb2k-devsolo is a Claude Code plugin for the Ship phase that connects DevSolo git MCP automation for linear history, branches, and PR workflows.
by slamb2k · github.com/slamb2k/devsolo
Install when you want Claude to drive DevSolo’s git MCP workflow for linear history, branch management, and PR automation without merge-conflict churn.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install slamb2k-devsolo@slamb2k/devsoloBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:slamb2k/devsolo") and the paste-ready config with skillselion.get_install_config("plugin:slamb2k/devsolo").
What it does
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. Solo builders 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.
Highlights
- 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
Why builders use it
Solo builders lose time to messy git history, manual PR steps, and merge conflicts that agents cannot fix without a structured git automation tool.
After install, Claude Code can use DevSolo MCP tools to manage branches and PRs while keeping linear history and fewer conflict-prone merges.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 1 stars, 0 votes.
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.
Comments
Share how you use slamb2k-devsolo, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.