skills.rest
furrycolombia-sys
furrycolombia-sysCOMMUNITY
Explore all skills by this author →
GitHub

review-branch

Identify and patch discrepancies between the current branch and develop.

1|Updated Mar 18, 2026
Search Tags:#automation#git#testing#review#diff#branch#patch
One-click install
npx skills add https://github.com/furrycolombia-sys/candyshop --skill review-branch-furrycolombia-sys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-branch
Source: https://github.com/furrycolombia-sys/candyshop/tree/main/.agents/skills/review-branch
Command: npx skills add https://github.com/furrycolombia-sys/candyshop --skill review-branch-furrycolombia-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and reconcile code on the current branch against develop by identifying and fixing defects, inconsistencies, and potential regressions across the codebase.

Core Features & Use Cases

  • Automated branch-diff analysis to surface all issues between branches.
  • Safe, patch-based fixes with validation and test runs to prevent breakage.
  • Use in pre-merge checks and CI pipelines to ensure branch parity with develop.

Quick Start

Run the review-branch skill to compare the current branch with develop, identify all issues, and apply safe fixes.

Frequently Asked Questions about review-branch

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

FAQPage Schema
How do I find and fix discrepancies between a git branch and develop?▼

To find and fix branch discrepancies, run an automated diff analysis against develop. This process identifies inconsistencies and applies safe, patch-based fixes while running test suites to prevent regressions before merging.

What is branch parity validation in a pull request workflow?▼

Branch parity validation is a pre-merge CI check that ensures your current branch has no unresolved issues or regressions compared to develop. It uses diff tooling and test suites to verify code changes before commit.

Do I need a test suite to automatically patch issues in a git diff?▼

Yes, a validation harness and test suites are required to safely patch issues. The tooling applies patches by verifying changes against the test suite before committing them to the repository.

Can I use automated branch review for pre-merge CI checks?▼

Yes, automated branch review is designed for pre-merge CI checks. It audits the current branch versus develop, applies safe fixes, and validates changes to ensure branch parity before merging.

What are the limitations of automatically fixing git branch discrepancies?▼

Automated fixing is limited to safe, patch-based fixes validated by a test harness. It requires a defined source-of-truth workflow and cannot safely patch issues that break existing test suites or validation checks.

Related Skills

Explore More Software Engineering Skills→
canonicalcanonical
29

migrate-harness-tests-to-state-transition-test

Migrate ops.testing Harness test suites to state-transition tests for Juju events.

Official
Advanced
beekeeper-labbeekeeper-lab
1

Deploy

Promote a test branch to main via pull request after tests and lint pass.

Community
Advanced
burgebjburgebj

ship

Automate testing, code review, pull request creation, and deployment workflows.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced