Receber por email
← Voltar para o catálogo

mk:jira-lifecycle

Drive JIRA workflow lifecycle via the jira-as wrapper: transition, assign, resolve, reopen, manage versions and components. Triggers: 'transition KEY to Status', 'mark KEY as Done', 'assign KEY to user', 'reopen KEY', 'release version', 'create component'. NOT for issue CRUD (mk:jira-issue); NOT for bulk transitions (mk:jira-bulk).

15estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add ngocsangyem/MeowKit

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/mk-jira-lifecycle/svg)](https://www.skillteca.com.br/skills/mk-jira-lifecycle)
#ai

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

mk:jira-lifecycle

Forks to the jira-lifecycle agent. lifecycle transition takes the issue key positional + a --to "Status Name" flag (or --id <transition_id>).

Workflow discovery is mandatory before suggesting transitions. The agent reads tasks/jira-workflows/ (instance-discovered cache) and runs bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/fetch-workflow.sh <KEY> if absent. See references/workflow-discovery.md. The references/patterns/*.md files are illustrative concepts only — they are NOT your project's actual workflow.

Triggers

  • "transition PROJ-123 to In Progress"
  • "mark PROJ-123 as Done with resolution Fixed"
  • "assign PROJ-123 to john.doe"
  • "reopen PROJ-123"
  • "release version v1.0.0 in PROJ"

Examples

  • Status change: "move PROJ-123 to In Review with comment 'ready for QA'"
  • Resolution-required: "close PROJ-456 with resolution Won't Fix"
  • Assignment: "assign all my open PROJ tickets to john.doe" (the agent will refuse — that's bulk; redirect to mk:jira-bulk)

See also

  • Agent: ../../agents/jira-lifecycle.md
  • Shared: ../jira/references/{install-and-auth,cli-idioms,safety-framework}.md
  • Authoritative source for THIS project's workflow (discovered, not templated):
  • references/workflow-discovery.md — discovery + caching protocol (READ FIRST)
  • tasks/jira-workflows/<workflow-slug>.md — discovered workflow definitions
  • tasks/jira-workflows/_schemes/<PROJECT_KEY>.md — project → workflow mapping
  • Discovery script: bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh ... — wrapped by fetch-workflow.sh
  • Domain refs:
  • references/workflow-transitions.md — common transition idioms + resolution-required patterns
  • Educational concept patterns (illustrative shapes, NOT authoritative for your instance — always prefer the discovered cache above):
  • references/patterns/standard-workflow.md — basic 3-state lifecycle (concept)
  • references/patterns/software-dev-workflow.md — engineering-team flow (concept)
  • references/patterns/jsm-request-workflow.md — JSM ITIL flow (concept)
  • references/patterns/incident-workflow.md — incident handling (concept)
  • Peer leaves: mk:jira-bulk (bulk transition; reads same workflow cache), mk:jira-jsm (JSM-specific transitions), mk:jira-collaborate (transition --comment body templates)

Gotchas

  • (none yet — grow from observed failures)
Compartilhar X LinkedIn