skills.rest
NavarrePratt
NavarrePrattCOMMUNITY
Explore all skills by this author →
GitHub

team-branch-fix

Coordinate parallel code fixes with per-file ownership and Codex MCP validation.

2|2|Updated Dec 30, 2025
Search Tags:#automation#code-review#git-workflow#agent-teams#codex-validation#parallel-fixes#lint-tests-build
One-click install
npx skills add https://github.com/NavarrePratt/claude-settings --skill team-branch-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-branch-fix
Source: https://github.com/NavarrePratt/claude-settings/tree/main/skills/team-branch-fix
Command: npx skills add https://github.com/NavarrePratt/claude-settings --skill team-branch-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and manage parallel code fixes from a structured review to improve software quality and consistency.

Core Features & Use Cases

  • Interview the user to decide which findings to fix and group work by file ownership
  • Spawn independent fix agents that operate in parallel with exclusive file ownership
  • Validate all changes with Codex MCP and run verification (lint/test/build) after completion
  • Use a review report from /team-branch-review or pasted input, enabling scalable fixes across large codebases

Quick Start

Provide a review report (or path to one) to start interviewing findings, group work by file, and spawn parallel fix agents with Codex validation.

Frequently Asked Questions about team-branch-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate parallel code fixes across multiple files from a review report?▼

You can coordinate parallel code fixes by interviewing findings from a structured review report, assigning exclusive file ownership, and spawning independent fix agents that operate simultaneously to improve software quality.

What is the best way to assign file ownership for multi-file code fixes?▼

Assigning file ownership for multi-file code fixes is handled through an interview-driven selection process that groups review findings by file, ensuring each fix agent operates with exclusive control over its assigned files.

How do I validate code changes after spawning parallel fix agents?▼

You validate code changes from parallel fix agents by using Codex MCP to verify results, followed by running automated lint, test, and build tasks to ensure post-fix software consistency.

Can I use a pasted review report to start automating parallel git workflow fixes?▼

Yes, you can use a pasted review report or a path to an existing one to start the interview process, group work by file ownership, and spawn parallel fix agents with automated Codex validation.

Does this parallel code fix workflow require a specific code review tool?▼

No specific code review tool is required; the workflow accepts a review report from a prior branch review or pasted input, enabling scalable fixes across large codebases without rigid tool dependencies.

What are the limitations of using independent agents for parallel code fixes?▼

Independent agents for parallel code fixes require exclusive per-file ownership to prevent conflicts, meaning overlapping changes in the same file cannot be processed simultaneously without manual grouping adjustments.

Related Skills

Explore More Software Engineering Skills→
devkadedevkade
2

pkm:monthly-review

Aggregate Obsidian weekly notes into a structured monthly summary.

Community
Advanced
ysyecustysyecust
40

verification-loop

Automate end-to-end project verification across builds, type checks, linting, tests, and security scans.

Community
Intermediate
NSEvteevNSEvteev
31

review

Unify local branch and GitHub PR reviews into a single workflow.

Community
Advanced
axel-kaliffaxel-kaliff

review-fix

Review and fix critical and warning issues in changed Python files.

Community
Advanced