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).
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
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.
mk:jira-bulk)../../agents/jira-lifecycle.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.mdreferences/workflow-discovery.md — discovery + caching protocol (READ FIRST)tasks/jira-workflows/<workflow-slug>.md — discovered workflow definitionstasks/jira-workflows/_schemes/<PROJECT_KEY>.md — project → workflow mappingbash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh ... — wrapped by fetch-workflow.shreferences/workflow-transitions.md — common transition idioms + resolution-required patternsreferences/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)mk:jira-bulk (bulk transition; reads same workflow cache), mk:jira-jsm (JSM-specific transitions), mk:jira-collaborate (transition --comment body templates)No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use this skill to generate well-branded interfaces and assets for MeowKit (AI Agent Toolkit for Claude Code), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
The English summary is being prepared. Showing the original description.
Turn a raw idea into ONE honest recommendation: interview one question at a time until confirmed, then give a verdict with trade-offs and a checklist. Not for options or debate.
The English summary is being prepared. Showing the original description.
Browser automation CLI for agents: navigate, click/fill, screenshot, extract data, test apps, Electron/Slack, cloud browsers. NOT for the user's real Chrome profile/cookies (mk:chrome-profile).
The English summary is being prepared. Showing the original description.
Detects the right agent and complexity tier at Phase 0 orient; runs first in every workflow. NOT for runtime agent routing inside a single skill.
The English summary is being prepared. Showing the original description.
Angular v20+ patterns: components, signals, services, forms, routing, HTTP, testing, SSR. Auto-activates on .ts files in Angular projects (angular.json detected).
The English summary is being prepared. Showing the original description.
Design and review durable REST, GraphQL, RPC, or event API contracts: shape, compatibility, pagination, error semantics. Discovers existing consumers first. Not implementation, schema, or release.
The English summary is being prepared. Showing the original description.