agentsclimarketplace

Mk jira dev

Skill ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/cursor/root/.cursor/skills/mk-jira-dev

Production ready. AI Agent Workflow System for Claude Code

Install
npx -y skills add ngocsangyem/MeowKit --skill mk-jira-dev

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate dev artifacts from Jira tickets via jira-as: branch names, PR descriptions, parsed commits, PR-to-issue links. NOT running git/gh (mk:ship) or issue CRUD (mk:jira-issue).

SKILL.md

1.6 KB, as published. Nobody here has run it

mk:jira-dev

Forks to the jira-dev agent. Pure artifact generation — the user reviews and runs the resulting git/gh commands.

Triggers

  • "branch name for PROJ-123"
  • "PR description for PROJ-123"
  • "parse commits in main..HEAD for issue keys"
  • "link this commit to PROJ-123"
  • "link this PR to PROJ-123"

Examples

  • Branch: "give me a branch name for PROJ-123"
  • PR: "draft a PR title and body from PROJ-123"
  • Smart-commit: "generate a 'Closes PROJ-123' footer for my last 5 commits"

Handoff

mk:ship may invoke bash $(git rev-parse --show-toplevel)/.cursor/skills/jira/scripts/jira-as.sh dev branch-name <KEY> during its branch-creation step (documentation-only — no automatic wiring exists today). Users opt in by passing the Jira key context to mk:ship.

See also

  • Agent: ../../agents/jira-dev.md
  • Shared: ../jira/references/{install-and-auth,cli-idioms,safety-framework}.md
  • Domain refs:
    • references/branch-naming.md — convention reference (<type>/<KEY>-<slug>)
    • references/smart-commits.md — smart-commit syntax for closing/transitioning from commit messages
    • references/commit-messages.md — Atlassian-aware commit-message conventions
  • Peer leaves: mk:ship (consumes dev branch-name + dev pr-description), mk:jira-issue (issue must exist before branch creation), mk:jira-lifecycle (transitions via smart-commit footer)

Gotchas

  • (none yet)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.