agentsclimarketplace

Jira dev

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

Production ready. AI Agent Workflow System for Claude Code

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

  • 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 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).

SKILL.md

2.2 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 $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)

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • Generate branch names from Jira keys
  • Generate PR descriptions from Jira keys
  • Parse commits for issue keys
  • Generate smart-commit footers for commits
  • Generate commit-to-issue links

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.