skills.rest
raulbethencourt
raulbethencourtCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

appmerge

Compare SugarCRM branches to detect lost custom code and generate risk reports.

2|Updated Jan 8, 2023
Search Tags:#merge#diff-analysis#custom-code#code-integrity#risk-report#sugarcrm
One-click install
npx skills add https://github.com/raulbethencourt/Fenix --skill appmerge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: appmerge
Source: https://github.com/raulbethencourt/Fenix/tree/main/dotfiles/.config/opencode/skills/appmerge
Command: npx skills add https://github.com/raulbethencourt/Fenix --skill appmerge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-merge integrity checks for SugarCRM projects to detect lost or damaged custom code after a version upgrade.

Core Features & Use Cases

  • Detect missing or altered client customizations after a merge
  • Generate a structured risk report highlighting CRITICAL, HIGH and MEDIUM findings
  • Produce optional patches and a PDF export workflow for audit trails

Quick Start

Provide OLD_BRANCH and NEW_BRANCH values and run the skill to produce a risk report and optional patch set.

Frequently Asked Questions about appmerge

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

FAQPage Schema
How do I detect missing custom code after a SugarCRM branch merge?▼

To detect missing SugarCRM custom code after a merge, compare an OLD_BRANCH and NEW_BRANCH to identify lost or altered client customizations. The tool auto-discovers affected files using custom markers and generates a structured risk report.

What is a post-merge diff analysis for SugarCRM upgrades?▼

A post-merge diff analysis for SugarCRM compares two branches to identify damaged or lost custom code following a version upgrade. It produces a risk report with severity findings and optional patches to ensure code integrity.

How do I generate a code integrity risk report with CRITICAL and HIGH findings?▼

You can generate a code integrity risk report by running a diff analysis between two SugarCRM branches. The output categorizes issues into CRITICAL, HIGH, and MEDIUM findings, and includes a PDF export workflow for audit trails.

What values do I need to provide to run a SugarCRM diff analysis?▼

To run the SugarCRM diff analysis, you need to provide OLD_BRANCH, NEW_BRANCH, CLIENT_NAME, and CUSTOM_MARKERS values. These inputs enable the tool to auto-discover client files and custom modules for comparison.

Can I generate patches for altered SugarCRM customizations after a merge?▼

Yes, you can generate optional patches for altered SugarCRM customizations after a merge. The diff analysis identifies the damaged code and produces a patch set alongside a structured risk report.

Related Skills

Explore More Software Engineering Skills→
supermalangsupermalang

visual-review

Read visual approval states for changed baseline images without modifying repository files.

Community
Advanced
vecearvecear

dependency-vulnerability-triage

Convert npm audit and Snyk reports into prioritized patch plans.

Community
Advanced
xuyannan0321xuyannan0321

test-and-review

Run linting and building checks to verify code quality before deployment.

Community
Basic
dalawwadalawwa

git:compare-worktrees

Compare Git worktrees and branches by executing path-level or full-worktree diffs.

Community
Advanced