mob
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: mob
description: Use when the user wants to set, change, or clear git commit co-authors for pair or mob programmi…
category: data
runtime: no special runtime
---
# mob output preview
## PART A: Task fit
- Use case: Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming. If arguments indicate solo work (e.g., "solo", "just me"): run git solo, report primary author, exit. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflow / 1. Solo Mode / 2. Load Co-authors” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming. If arguments indicate solo work (e.g., "solo", "just me"): run git solo, report primary author, exit. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Workflow / 1. Solo Mode / 2. Load Co-authors” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/mob`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Workflow / 1. Solo Mode / 2. Load Co-authors”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: mob
description: Use when the user wants to set, change, or clear git commit co-authors for pair or mob programmi…
category: data
source: majiayu000/claude-skill-registry
---
# mob
## When to use
- Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming. If arguments indic…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Workflow / 1. Solo Mode / 2. Load Co-authors” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "mob" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflow / 1. Solo Mode / 2. Load Co-authors
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Mob Programming Co-author Manager
Workflow
1. Solo Mode
If arguments indicate solo work (e.g., "solo", "just me"): run git solo, report primary author, exit.
2. Load Co-authors
Use git mob -p to find coauthors file, read with Read tool, parse JSON for available co-authors and initials.
3. Match Names to Initials
Match each name: exact initials → name substring (case-insensitive) → email prefix. If ambiguous, ask user to clarify.
4. Handle Unknown Names
If no match:
- Infer email from existing patterns (domain, naming convention)
- Generate initials from name (avoid collisions)
- Prompt for confirmation (show initials, name, inferred email)
- Run
git add-coauthor <initials> "<name>" <email>
5. Set Mob
Run git mob <initials...> with resolved initials.
6. Report
Show primary author and all co-authors with names.
Example
/mob alice dana
→ alice → aw (Alice Wong)
→ dana not found → infer dana@acme.com → add as dw
→ git mob aw dw
Edge Cases
Handle: missing coauthors file (create it), empty args (show status), ambiguous matches (prompt), mixed known/unknown (resolve known first).
Decide Fit First
Design Intent
How To Use It
Boundaries And Review