Skip to content

Add release skill - #16

Closed
cs-raj wants to merge 1 commit into
mainfrom
feat/add-release-skill
Closed

cs-raj wants to merge 1 commit into
mainfrom
feat/add-release-skill

Conversation

@cs-raj

@cs-raj cs-raj commented Aug 16, 2026

Copy link
Copy Markdown

Summary

  • Adds the release skill — end-to-end release automation for Claude Code
  • Covers 8 steps: Jira ticket fetch, GitHub PR verification, release notes generation, deployment plan, rollback plan, release PRs, CAB Google Sheet, and SDK Confluence changelog table
  • Supports --dry-run mode (full preview, zero writes)

Security

All org-specific values have been removed. Nothing hardcoded:

  • No Jira account IDs, project keys, or domain names
  • No Google OAuth tokens or client IDs
  • No Confluence page IDs or Google Sheet template IDs
  • No person names or internal identifiers

Users configure their own values locally via references/config.json and references/google-credentials.json — both are gitignored. Example files with placeholders are provided.

Install

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

First-time setup (per user)

  1. Copy references/config.example.json → references/config.json and fill in your org's values
  2. Copy references/google-credentials.example.json → references/google-credentials.json and follow the OAuth setup in SKILL.md Step 6

Test plan

  • Install skill and verify /release triggers the help block
  • Run --dry-run against a real fix version — verify all 8 step summaries print without writing anything
  • Confirm google-credentials.json and config.json are not included in the repo

🤖 Generated with Claude Code

End-to-end release automation skill covering Jira ticket fetch,
GitHub PR verification, deployment/rollback plan generation, release
PR creation, CAB Google Sheet population, release notes ticket
creation, and SDK Confluence changelog table generation.

All org-specific values (project keys, account IDs, Confluence page
IDs, Google Sheet template IDs, OAuth credentials) are excluded from
the repo. Users configure their own values via references/config.json
and references/google-credentials.json (both gitignored). Example
files with placeholder values are provided.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@cs-raj
cs-raj requested a review from a team August 16, 2026 10:53
@github-actions

Copy link
Copy Markdown

🔒 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

@timbenniks-contentstack

Copy link
Copy Markdown
Contributor

Thanks @cs-raj for putting this together! We're not including it in this bundle, though. This repo is the public set of Contentstack product skills for customers (CMS, SDKs, Live Preview, Launch, Studio…), and this skill automates our internal engineering workflow (our release process: CAB sheet, TD tickets, SDK changelog). It also stores Google OAuth credentials in the skill folder, and the name release would compete with the customer-facing cms-releases skill. It would be a great fit for an internal engineering skills repo. Happy to help set one up. We're shipping the current bundle as one release in #21, so I'm closing this here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants