Analyze fork divergence, conflicts, and upgrade paths for Helm chart forks.
Analyzes Helm chart fork divergence, conflicts, and upgrade paths for safe merges.
/plugin marketplace add MisterGrinvalds/charts/plugin install mistergrinvalds-charts@MisterGrinvalds/chartsAnalyze fork divergence, conflicts, and upgrade paths for Helm chart forks.
This agent performs deep analysis of chart forks to help with:
# Get fork status
cd forks/<chart>
git fetch upstream
# Commits behind
git rev-list --count HEAD..upstream/main
# Commits ahead (local customizations)
git rev-list --count upstream/main..HEAD
# Modified files
git diff --name-only upstream/main
# Detailed diff stats
git diff --stat upstream/main
Group changes by type:
Check for overlapping modifications:
# Files modified in both local and upstream
git diff --name-only HEAD...upstream/main
Fork Analysis: cert-manager
═══════════════════════════════════════════════════════════════
Upstream: https://github.com/cert-manager/cert-manager
Fork: https://github.com/MisterGrinvalds/cert-manager
Branch: main
Divergence Summary:
Upstream version: v1.14.0
Fork version: v1.13.0 + 5 local commits
Commits behind: 47
Commits ahead: 5
───────────────────────────────────────────────────────────────
LOCAL CUSTOMIZATIONS (5 commits)
───────────────────────────────────────────────────────────────
1. abc1234 - Add custom resource limits for local dev
Files: values.yaml
2. def5678 - Add prometheus servicemonitor
Files: templates/servicemonitor.yaml (new)
3. ghi9012 - Customize webhook configuration
Files: templates/webhook-deployment.yaml
4. jkl3456 - Add node selector for arm64
Files: values.yaml, templates/_helpers.tpl
5. mno7890 - Update default replicas
Files: values.yaml
───────────────────────────────────────────────────────────────
UPSTREAM CHANGES (47 commits since fork)
───────────────────────────────────────────────────────────────
Breaking Changes:
- [BREAKING] Webhook now requires cert-manager.io/v1 API
- [BREAKING] Removed deprecated --leader-elect flag
Notable Updates:
- Security fix: CVE-2024-xxxx patched
- New feature: ACME external account binding
- Performance: Reduced memory usage by 30%
Modified Files:
templates/ 15 files changed
values.yaml 1 file changed
Chart.yaml 1 file changed
───────────────────────────────────────────────────────────────
CONFLICT ANALYSIS
───────────────────────────────────────────────────────────────
High Risk (likely conflicts):
- values.yaml
Local: Added custom resources section
Upstream: Restructured resources section
Recommendation: Manual merge required
Medium Risk (review needed):
- templates/webhook-deployment.yaml
Local: Added custom annotations
Upstream: Updated container spec
Recommendation: May merge cleanly, verify result
Low Risk (should merge cleanly):
- templates/servicemonitor.yaml
Local: New file (addition)
Recommendation: Will preserve local addition
───────────────────────────────────────────────────────────────
UPGRADE RECOMMENDATION
───────────────────────────────────────────────────────────────
Recommended approach: Incremental merge
Steps:
1. Backup current fork state
2. Merge upstream/main with --no-commit
3. Resolve conflicts in values.yaml manually
4. Test helm template output
5. Run /charts-values-validate cert-manager
6. Commit merge
Estimated effort: Medium (1-2 conflicts to resolve)
Alternative: Rebase (cleaner history, but rewrites local commits)
/charts-fork-sync <chart> - Execute the sync after analysis/charts-fork-list - See all forks and their status/charts-values-validate <chart> - Validate after mergeUse this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Examples: <example>Context: User is running /hookify command without arguments user: "/hookify" assistant: "I'll analyze the conversation to find behaviors you want to prevent" <commentary>The /hookify command without arguments triggers conversation analysis to find unwanted behaviors.</commentary></example><example>Context: User wants to create hooks from recent frustrations user: "Can you look back at this conversation and help me create hooks for the mistakes you made?" assistant: "I'll use the conversation-analyzer agent to identify the issues and suggest hooks." <commentary>User explicitly asks to analyze conversation for mistakes that should be prevented.</commentary></example>