Shared workflows for git, PRs, issues, and worktrees
npx claudepluginhub month2month/m2m-developer-plugin --plugin m2m-developerSync default branch, create feature branch, commit staged changes, push, and open a pull request. Use when user asks to "commit and PR", "push and create PR", or "send this up for review".
Create a fresh feature or fix branch from the latest default branch. Use when user wants to start new work on a clean branch, e.g. "create a branch for X", "start a new feature branch", "new branch for fixing Y".
Finalize a pull request by fixing test/lint/build failures, running CI checks, updating PR description, and marking ready for review. Auto-detects project type (Rails, Node, Python, Go, Rust, etc.). Handles the feedback loop for PRs where code is written but CI is failing or docs are incomplete. Use when user asks to "finish this PR", "complete the PR", "fix PR failures", or "update PR description".
Analyze and fix GitHub issues end-to-end. Auto-detects project type (Rails, Node, Python, Go, Rust, etc.), fetches issue details, implements fixes, writes tests, runs CI checks, and creates PRs. If CI checks fail, retries up to 5 times. After 5 failed attempts, creates a draft PR and escalates. Use when user asks to fix or work on a GitHub issue.
Move uncommitted work (staged, unstaged, and untracked files) from the current branch onto a new feature branch created from the latest default branch. Use when user has changes on the wrong branch or wants to start a clean feature branch with current work.
Check out default branches and pull latest for all repos in the current workspace
This skill should be used when the user asks to "create a worktree", "set up a worktree", "work in a new branch", "start a new task branch", "worktree for issue", or wants to work on a separate branch without disrupting their current working directory. Manages git worktrees for parallel development.
Claude Code plugin with shared developer skills for the M2M team.
| Skill | Command | When to use | Description |
|---|---|---|---|
| finish-pr | /m2m-developer:finish-pr 123 | PR pipeline is failing, fix it locally instead of @claude on GH | Fix failing CI, update description, mark PR ready for review |
| fix-issue | /m2m-developer:fix-issue 42 | Well-specced issue, go from zero to PR | Fix a GitHub issue end-to-end: fetch, branch, implement, test, PR |
| commit-push-pr | /m2m-developer:commit-push-pr | Local changes ready to go, need branch + commit + PR in one shot | Sync default branch, create feature branch, commit, push, open PR |
| sync-repos | /m2m-developer:sync-repos | Parent dir with many repos that need to be up to date | Pull latest on default branches for all repos in workspace |
| move-changes-to-branch | /m2m-developer:move-changes-to-branch feat/thing | Uncommitted changes on wrong branch, need to move them | Stash work, sync default branch, create feature branch, restore and commit |
| create-feature-branch | /m2m-developer:create-feature-branch feat/thing | Starting new work, need a clean branch | Create a fresh feature branch from latest default branch |
| worktree | /m2m-developer:worktree feat/new-thing | Tackle a feature/issue without disrupting other sessions | Create an isolated git worktree branched off default |
You see a PR — yours or one Claude made — and the pipeline is failing. Instead of leaving a @claude comment on GitHub and waiting, just clone/cd into the repo locally and run:
/m2m-developer:finish-pr 123
Claude runs locally, so it can actually execute the tests, see what's broken, fix it, and push — all without the back-and-forth of GitHub comment-driven fixes.
You have a well-specced GitHub issue and want to go from zero to PR. Just point Claude at the issue number:
/m2m-developer:fix-issue 42
It fetches the issue, creates a branch, implements the fix, writes tests, runs CI checks, and opens a PR. Best used when the issue has enough detail for Claude to work autonomously.
You've been working locally — changes are sitting uncommitted, maybe you're on main, maybe on a random branch. Doesn't matter. This skill handles the full flow:
/m2m-developer:commit-push-pr
It syncs the default branch, creates an appropriately named feature branch, commits your changes, pushes, and opens a PR. Works no matter where you are in the git tree.
You've been hacking on main or a stale branch and realize your changes belong on a proper feature branch:
/m2m-developer:move-changes-to-branch feat/new-search
It stashes everything (including untracked files), syncs the default branch, creates a new branch, restores your work, and commits it. If you don't provide a branch name, it'll ask.
You're about to start new work and want a clean branch off the latest default:
/m2m-developer:create-feature-branch fix/login-redirect
Syncs the default branch and creates a new branch from it. If you have uncommitted changes, it warns you and suggests move-changes-to-branch instead.
You want to tackle a feature or issue without disrupting your current working directory or other Claude sessions:
/m2m-developer:worktree fix/login-bug
Creates an isolated git worktree branched off the default branch. Useful when you're juggling multiple things and don't want context bleed between tasks.
Pull latest on all repos in your workspace at once:
/m2m-developer:sync-repos
Most useful when you're working from a parent directory with many child repos that all need to be synced before you start a new prompt. Also handy when you just need fresh context and up-to-date repos without running the git commands yourself.
Add the marketplace (one-time setup):
/plugin marketplace add Month2Month/m2m-developer-plugin
Install the plugin:
/plugin install m2m-developer@Month2Month
claude --plugin-dir /path/to/m2m-developer-plugin
skills/ with the skill nameSKILL.md file with YAML frontmatter and instructionsclaude --plugin-dir .Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,393 supported skills.
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, and 16+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.