joncol/jira
homedir/.claude/skills/jira/SKILL.md
Fetch Jira issue details for the current branch or a given issue key. Only use when working in a project whose path contains "kontrakcja".
data-ai
Updated Apr 6, 2026
$ install --global
skillsauthnpx skillsauth add joncol/dotfiles jiraInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 10:45 AM225.9s4 files scanned
SKILL.md
- name:
- jira
- description:
- Fetch Jira issue details for the current branch or a given issue key. Only use when working in a project whose path contains "kontrakcja".
- argument-hint:
- [ISSUE-KEY]
Fetch and display Jira issue details.
First-time setup
If ~/.claude/jira-tokens.json does not exist, tell the user to run ~/.claude/skills/jira/auth.sh to authorize via OAuth, then retry.
Steps
-
Fetch the issue JSON using
fetch.sh(it handles token refresh, cloud ID, and the API call internally):- If
$ARGUMENTSis provided, use it as the issue key:~/.claude/skills/jira/fetch.sh CORE-1234 - Otherwise, use
--from-bookmarkto auto-detect the issue key from the current jj bookmark:~/.claude/skills/jira/fetch.sh --from-bookmark - If
fetch.shfails with a bookmark error, ask the user for the issue key. - If it fails with a token error, tell the user to run
~/.claude/skills/jira/auth.shto re-authorize.
- If
-
Present the issue in a readable format:
- Key: issue key
- Type: issue type (Bug, Story, Task, etc.)
- Status: current status
- Priority: priority level
- Summary: title
- Assignee: who it's assigned to
- Reporter: who created it
- Description: the issue description (summarize if very long)
- Recent comments: show the last 5-6 comments if any exist (author, date, body). Do NOT use blockquotes (
>) for comment bodies — they render with low-contrast styling. Use plain text under a bold Author — Date: header instead.
Related Skills
joncol/wl-copy
tools
VerifiedTrustedCommunity
Copy the last code snippet or message to the system clipboard
SKILL.mdUpdated Apr 6, 2026
joncol/review-pr
data-ai
VerifiedTrustedCommunity
Review a PR by comparing the Jira ticket requirements against the actual implementation. Only use when working in a project whose path contains "kontrakcja".
SKILL.mdUpdated Apr 6, 2026
joncol/prune-sessions
development
VerifiedTrustedCommunity
List and delete old Claude Code sessions. Shows all sessions with dates and summaries, and lets the user pick which ones to remove.
SKILL.mdUpdated Apr 6, 2026
joncol/pr-comments
documentation
VerifiedTrustedCommunity
Fetch and display GitHub PR review comments for the current branch or a given PR number. Only use when working in a project whose path contains "kontrakcja".
SKILL.mdUpdated Apr 6, 2026