Qmu Workaholic
qmu-workaholic is a Claude Code plugin for the Build phase that applies qmu’s standard ticket-driven branch, commit, and pull-request workflow configuration.
by qmu · github.com/qmu/workaholic
Adopt qmu’s standard Claude Code setup so agent work stays aligned with tickets, branches, commits, and pull requests.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install qmu-workaholic@qmu/workaholicBuilt 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:qmu/workaholic") and the paste-ready config with skillselion.get_install_config("plugin:qmu/workaholic").
What it does
qmu-workaholic is a Claude Code plugin bundle that ships the standard Claude Code configuration used in the qmu workaholic repository. It is aimed at builders and small teams who want agent-assisted coding to follow a ticket-driven rhythm—branching, committing, and opening pull requests—instead of ad hoc edits. The catalog metadata highlights development, core workflow, and pull-request-oriented keywords, which signals that the plugin encodes process expectations rather than a one-off API or UI generator. Solo and indie developers who clone or mirror qmu’s setup can register this plugin to reduce drift between humans and agents on how work is scoped and delivered. It is not a full issue tracker; it is configuration and skills alignment for Claude Code inside that repo’s way of working. Install when you already use or plan to standardize on qmu’s workaholic workflow and want Claude to participate in the same ticket and PR loop as the rest of the team.
Highlights
- Single bundled plugin: one standard Claude Code configuration for the qmu/workaholic repo
- Ticket-driven workflow keywords: branch, commit, pull request, and core development flow
- Org-standard defaults so every session follows the same workaholic conventions
- Focused on development workflow automation with Claude Code, not generic chat prompts
- Lightweight catalog entry (1 plugin) for teams already in the qmu ecosystem
Why builders use it
Agent sessions drift from your team’s ticket and PR process when Claude Code is configured differently in every repo.
After you add the plugin, Claude Code sessions in workaholic-aligned repos follow one shared ticket-driven git workflow instead of inconsistent local setups.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is qmu-workaholic for?
It is for developers and small teams standardizing on the qmu workaholic repository who want Claude Code wired into the same ticket-driven branch, commit, and pull-request habits.
When should I use qmu-workaholic?
Use it when you are onboarding Claude Code on a workaholic-style project and need one canonical configuration instead of reinventing workflow rules per machine.
How do I add qmu-workaholic to my agent?
Install or register the plugin from the qmu/workaholic Claude Code plugin source in Claude Code, then open the repo so the bundled configuration applies to sessions in that project.
Comments
Share how you use qmu-workaholic, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.