SkillsAdd

upex-galaxy/agentic-qa-boilerplate

jira-administration

Run bounded Jira administration workflows for project Components or Atlassian instance migration.

First seen Aug 24, 2026

Installation

$ npx skills add upex-galaxy/agentic-qa-boilerplate --skill jira-administration
View on skills.sh ↗ GitHub repository ↗

Summary

  • Run bounded Jira administration workflows for project Components or Atlassian instance migration.
  • Use for jira-components, sync Jira components, jira-instance-migration, changed Jira URL, or repoint Jira.
  • Both modes are sealed behind read-first analysis and explicit user approval before any Jira, credential-session, or repository mutation.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from upex-galaxy/agentic-qa-boilerplate · top by installs.

npx skills add upex-galaxy/agentic-qa-boilerplate
test-automation 25 test-documentation 24 sprint-testing 24 regression-testing 23 acli 22 xray-cli 21 project-discovery 21 agentic-qa-core 16 git-flow-master 16 agentic-qa-onboard 15

Browse all from upex-galaxy/agentic-qa-boilerplate

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Declared
Codex Declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Repository health

Stars 21
License LICENSE
Default branch main
Open issues 6
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Compatibilityclaude-code, copilot, cursor, codex, opencode
Declared agents claude-code cursor codex github-copilot opencode

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,109 B
  • docs SUMMARY.md 368 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Jira Administration

Mode routing

Choose exactly one mode and load only its reference.

Mode Legacy alias / trigger Reference
components jira-components, reconcile/sync Jira Components references/components.md
instance-migration jira-instance-migration, changed/repoint Jira instance references/instance-migration.md

If the mode is unclear, ask. Never combine both modes in one run.

Compact Rules

The sealed mutation contract. Binding on every run of either mode:

  • Exactly ONE mode per run: components (references/components.md) or instance-migration (references/instance-migration.md). Load only that mode's reference. Never combine the two, never fall through into the other.
  • Mode unclear → ASK. Do not infer one from a bare "fix Jira" / "sync Jira" request.
  • Load /acli before any Jira operation. Load other tool-owner skills only when the selected reference requires them.
  • Missing MCP or Jira credentials = HARD STOP (AGENTS.md Critical Rule #10). Name the exact env var, point at .env / .env.example, ask for an agent-session restart. No workaround, no partial run.
  • Read-first on every mutation: inspect the live state before authoring any plan. Nothing is created, applied, deleted, or repointed without the user's explicit approval given inside the same run.
  • components: derive and inspect → author the plan file → dry-run → WAIT for explicit approval → only then --apply.
  • instance-migration: resolve and confirm BOTH instances → audit and verify reachability → WAIT for explicit approval → only then change files or the acli session. That session lives at ~/.config/acli and is machine-global: re-login repoints every repo on the host, not just this one.
  • The Atlassian host lives in .agents/project.yaml → issuetracker.atlassianurl and NOWHERE else locally. A stale ATLASSIAN_URL in .env or the process environment is contamination to DELETE, never to update — a second copy is what goes stale.
  • Template-repo carve-out: if .agents/project.yaml → project.projectname is null, the repo is an un-onboarded template. Leave atlassianurl and project_key null, say so in the report, and never manufacture a commit to hide the emptiness.
  • Run only the selected reference's verification steps. Never run the other mode's.
  • Forward $ARGUMENTS unchanged.

Read full SKILL.md when: the mode is ambiguous, a dry-run diff or migration audit looks wrong, or you need the selected reference's step-by-step phases and verification list.