agentsclimarketplace
Sign in

Jira dev

Skill ngocsangyem/MeowKit/.claude/skills/jira-dev

Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).From its SKILL.md

Install
npx -y skills add ngocsangyem/MeowKit --skill 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

  • 14 stars14 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.

SKILL.md

2.2 KB, 390 tokens by cl100k_base, 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 $CLAUDE_PROJECT_DIR/.claude/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)

What ships with it: 3 files

7.5 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 325,949. 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.