AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Mk:jira Dev

skill-ngocsangyem-meowkit-jira-dev · by ngocsangyem

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

↗ Website ↗ Repository
— No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-ngocsangyem-meowkit-jira-dev

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Mk:jira Dev? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 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 (/-)
  • 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)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Productivity