parallel-agents
jssblck/agents
Coordinate concurrent agent work and prevent merge conflicts in shared codebases.
What is parallel-agents?
Manages file ownership and merge strategies when multiple agents work in parallel on the same codebase. Use this when you encounter recurring merge conflicts, need to maintain AGENTS.md or CLAUDE.md documentation, or want to establish clear boundaries for independent work.
- Assign independent behavior to separate files to create ownership boundaries and reduce conflicts
- Structure shared lists for safe merging with one item per line and stable insertion order
- Identify and resolve repeated conflict hotspots through audit and structural repair
- Separate structural refactoring from behavior changes to keep commits clean
- Maintain concise agent documentation with working agreements and setup entry points
How to install parallel-agents
npx skills add https://github.com/jssblck/agents --skill parallel-agentsHow to use parallel-agents
- 1.Review the conflict history or hotspots in your shared files to identify patterns
- 2.Choose the appropriate reference guide: one-feature-one-file.md for boundaries, mergeable-edits.md for registry formatting, hotspot-audit.md for conflict analysis, or doc-gardening.md for documentation
- 3.Apply the recommended structural changes: create separate files for independent work, reformat shared lists to one item per line, or consolidate duplicated documentation
- 4.Keep structural moves separate from behavior changes in distinct commits
- 5.Regenerate any generated files or lockfiles after applying changes
Use cases
- Multiple agents modifying the same configuration or registry files simultaneously
- Resolving recurring merge conflicts in shared documentation or agent instructions
- Establishing file boundaries when adding new agent features to a parallel workflow
- Auditing conflict history to determine whether code should be split into separate modules
- Regenerating lockfiles and generated files after concurrent edits
- Teams running multiple coding agents in the same repository
- DevOps or platform engineers managing agent coordination
- Developers maintaining shared agent configuration or documentation
- Projects with high concurrent development velocity
parallel-agents FAQ
Split when it creates a useful ownership boundary and independent agents can own separate files. Do not split merely to achieve a one-line registration in a shared registry.
Use one item per line, maintain stable insertion order, and avoid unrelated reformatting. This makes concurrent edits mergeable without conflicts.
Keep documentation concise: working agreements, non-obvious constraints, and useful setup or check entry points. Keep module-specific detail near the code that owns it.
Audit the conflict history first to understand the pattern. Then decide whether to split the file, reformat it for merging, or consolidate duplicated sections.
No. Keep structural moves (file splits, registry reformatting) separate from behavior changes in distinct commits for clarity and easier review.
Full instructions (SKILL.md)
Source of truth, from jssblck/agents.
name: parallel-agents description: "Use when agents work concurrently in a codebase, shared files have recurring merge conflicts, or AGENTS.md or CLAUDE.md needs maintenance."
Parallel agents
Keep independently owned work from colliding in shared files. Apply structural changes when concurrent work or observed conflict history justifies them.
- Give independent behavior its own file when that creates a useful ownership boundary. Keep edits to shared registries small. Do not split a cohesive module merely to achieve a one-line registration.
- Shape shared lists for merging: one item per line, stable insertion order, and no unrelated reformatting. Regenerate generated files and lockfiles.
- Investigate repeated conflict hotspots before splitting them. Keep structural moves separate from behavior changes when both are requested.
- Keep agent docs concise: working agreements, non-obvious constraints, and useful setup/check entry points. Keep module detail near its owner.
References
Read only the reference relevant to the task:
- one-feature-one-file.md: choosing file boundaries for concurrent feature work.
- mergeable-edits.md: editing shared registries, generated files, or conflicting branches.
- hotspot-audit.md: measuring conflict hotspots when an audit or structural repair is requested.
- doc-gardening.md: maintaining agent instructions or reducing duplicated documentation.
Related skills
More from jssblck/agents and the wider catalog.
ship-it
Commit, push, and open a PR with CI verification for completed changes.
tag-release
Tag and cut patch, minor, or major releases with verified commit, convention-matching tags, and green CI.
using-sops
Manage encrypted secrets in repos using sops and age identities.
code-craft
Apply established engineering conventions for architecture, typing, error handling, and abstraction decisions.
markitdown
Convert PDFs, Word, PowerPoint, Excel, images, audio, and web content to Markdown for LLM pipelines.
brief-to-tasks
Break design briefs into ordered, independently buildable tasks using vertical slices.