jm96441n/.config/opencode/skill/jira
.config/opencode/skill/jira/SKILL.md
# Jira Skill Guidelines for creating and managing Jira issues for HashiCorp projects. ## InfraGraph Project (IG) ### Project Information - **Project Key**: `IG` - **Team Field**: `customfield_10001` - **Default Team Value**: `"InfraGraph-Graph Engine"` ### Creating Issues When creating Jira issues for the InfraGraph project, always include the team field: ```python jira_create_issue( project_key="IG", summary="Task summary", issue_type="Task", description="Task description
$ install --global
skillsauthnpx skillsauth add jm96441n/dotfiles .config/opencode/skill/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, 9:23 AM400.4s1 file scanned
SKILL.md
Jira Skill
Guidelines for creating and managing Jira issues for HashiCorp projects.
InfraGraph Project (IG)
Project Information
- Project Key:
IG - Team Field:
customfield_10001 - Default Team Value:
"InfraGraph-Graph Engine"
Creating Issues
When creating Jira issues for the InfraGraph project, always include the team field:
jira_create_issue(
project_key="IG",
summary="Task summary",
issue_type="Task",
description="Task description",
additional_fields={
"customfield_10001": {"value": "InfraGraph-Graph Engine"}
}
)
Linking to Epics
When creating issues under an epic, use the parent field in additional_fields. This automatically inherits the team field from the parent epic:
jira_create_issue(
project_key="IG",
summary="Subtask summary",
issue_type="Task",
description="Task description",
additional_fields={
"parent": "IG-1234"
}
)
Note: When linking to an epic via parent, you don't need to explicitly set customfield_10001 as it will be inherited.
Common Issue Types
- Epic: Large features that need to be broken down
- Task: Standard work items
- Story: User-facing features
- Bug: Defects or issues
- Subtask: Use
parentfield to link to parent issue
Best Practices
- Always check the parent epic's team field when creating child issues
- Use descriptive summaries that clearly state the objective
- Include clear success criteria in the description
- Link related issues appropriately
- Set appropriate priority and labels when creating issues
Related Skills
jm96441n/session-close
tools
VerifiedTrustedCommunity
Protocol for properly ending a coding session - ensures all work is committed, pushed, and handed off correctly.
39SKILL.mdUpdated Apr 6, 2026
jm96441n/jujutsu
tools
VerifiedTrustedCommunity
Prefer Jujutsu (jj) over git for version control. Use squash workflow pattern where commits are described first, then changes are made in a scratch child commit and squashed into the parent.
39SKILL.mdUpdated Apr 6, 2026
jm96441n/gremlin
development
VerifiedTrustedCommunity
Write Gremlin graph traversal queries for Neptune using the gremlin-go driver patterns in this codebase
39SKILL.mdUpdated Apr 6, 2026
jm96441n/ast-grep
development
VerifiedTrustedCommunity
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search.
39SKILL.mdUpdated Apr 6, 2026