AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Jira Release Setup

skill-aipcc-cicd-claudio-skills-jira-release-setup · by aipcc-cicd

Create the complete Jira card structure for a product release milestone. Encodes the release card templates (epics + child tasks) so the agent never has to reconstruct them. Use this skill when the user asks to set up Jira cards for a new release, create release tracking epics, or set up sprint cards for a release milestone.

↗ Repository
— No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-aipcc-cicd-claudio-skills-jira-release-setup

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aipcc-cicd-claudio-skills-jira-release-setup)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Jira Release Setup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Jira Release Setup

Creates the complete Jira card structure for a product release milestone. Encodes the canonical release templates so no business logic needs to be reconstructed each session.

Prerequisites

Required environment variables:

  • JIRA_SITE — Atlassian site (e.g. yourorg.atlassian.net)
  • JIRA_TOKEN — Atlassian API token
  • JIRA_EMAIL — Your Atlassian account email

Required tools: acli, jq

Card Templates

Two-phase release (default)

Epic:   Downstream Release
  ├── Task: Build   RC drops
  ├── Task: Release   to production
  └── Task: Send a   release announcement email

Epic:   Post-Release Activities
  ├── Task: Push   to cloud marketplaces
  └── Task: Bump  version to

Single-epic release (--single-epic)

Epic:   Downstream Release
  ├── Task: Release   to production
  ├── Task: Send a   release announcement email
  └── Task: Bump  version to

Version Calculation

Next-version is computed automatically by _next_version.sh:

| Input version | Next version | |---|---| | 3.4 GA | 3.4.1 | | 3.3.2 | 3.3.3 | | 3.4 EA1 | 3.4 EA2 |

Scripts

create_release.sh — Create full release card structure

./scripts/create_release.sh --project KEY   [options]

Options:

  • --project KEY — Jira project key (required)
  • --component NAME — component to set on all created issues (optional)
  • --single-epic — create one downstream epic only (default: two-phase)
  • --sprint-id ID — assign all created cards to this sprint (optional)

Examples:

# Single-epic release
./scripts/create_release.sh --project MYPROJ MyProduct "3.3.2" --single-epic

# Two-phase release assigned to sprint
./scripts/create_release.sh --project MYPROJ MyProduct "3.4 GA" --sprint-id 44147

# Get sprint ID first, then create
SPRINT=$(../../jira-sprint-manager/scripts/get_sprint_id.sh --board-id 42 --active)
./scripts/create_release.sh --project MYPROJ MyProduct "3.3.2" --single-epic --sprint-id "$SPRINT"

_next_version.sh — Calculate next version (internal helper)

./scripts/_next_version.sh "3.3.2"   # → 3.3.3
./scripts/_next_version.sh "3.4 GA"  # → 3.4.1
./scripts/_next_version.sh "3.4 EA1" # → 3.4 EA2

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Productivity