Qmu Workaholic
- 1 repo stars
- Updated July 27, 2026
- qmu/workaholic
qmu-workaholic is a Claude Code plugin that applies qmu’s standard ticket-driven branch, commit, and pull-request workflow configuration.
About
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 developers 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. 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.
- 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
Qmu Workaholic by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install qmu-workaholic@qmu/workaholicAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | July 27, 2026 |
| Repository | qmu/workaholic ↗ |
What it does
Adopt qmu’s standard Claude Code setup so agent work stays aligned with tickets, branches, commits, and pull requests.
Who is it for?
Best when you already use or adopting the qmu workaholic repo and want Claude Code to match your branch-and-PR ticket workflow.
Skip if: Skip if you need generic Claude Code starters with no tie to qmu’s repository or ticket-driven conventions.
What you get
After you add the plugin, Claude Code sessions in workaholic-aligned repos follow one shared ticket-driven git workflow instead of inconsistent local setups.
- Standard Claude Code configuration applied for workaholic-style repos
- Consistent agent behavior around branch, commit, and PR-oriented development
- Single-plugin bundle (pluginCount 1) from the qmu/workaholic catalog entry
By the numbers
- Catalog lists pluginCount: 1 for qmu/workaholic
- Plugin keywords include branch, commit, core, development, pullrequest, ticketdriven, workflow
- Repository slug: qmu-workaholic (source qmu/workaholic)
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Org-standard Claude Code configuration plugin, not an MCP server or a marketplace of unrelated skills.
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.