feat: add back-merge skill

[cs-raj]

Summary

• Adds the back-merge skill for checking and creating back-merge PRs (main/master → development) across repos after a release
• Fully generic — no hardcoded org IDs, Jira domains, or project keys

What the skill does

Two input modes:

• fixVersion — queries Jira for all repos touched in a release (project key extracted automatically from the fixVersion string)
• Repo list — paste GitHub URLs directly
• Both — combine both sources

Two run modes:

• check — read-only audit showing what needs back-merging (default)
• create — raises PRs for all repos that need them (confirmation required)

How to use

/back-merge "PROJ | 16-08-2026 | Release" check
/back-merge https://github.com/org/repo1 https://github.com/org/repo2
/back-merge "PROJ | 16-08-2026 | Release" create

How to install

npx skills add git@github.com:contentstack/contentstack-agent-skills.git --skill back-merge

Requirements

Tool	Install	Auth
gh CLI	brew install gh	gh auth login
Jira MCP	configured in Claude Code	— (fixVersion mode only)

🤖 Generated with Claude Code

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	0	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed