jira
Conventions for creating and managing Jira tickets
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Conventions for creating and managing Jira tickets
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
General Spacelift usage, Spacelift Terraform provider conventions, and Spacelift MCP integration
Dockerfile and container image conventions for building lean, secure images
Python coding conventions, tooling preferences, and style rules
Terraform and HCL coding conventions, formatting rules, and best practices
YAML file formatting conventions and style rules
| name | jira |
| description | Conventions for creating and managing Jira tickets |
atlassianUserInfo at creation time)Use the format <repo or project>: <description>. The description should be
a concise summary of the work, not a list of files or commits.
Write high-level descriptions of the task and any relevant context. Focus on the what and why, not on specific code changes, commits, or file paths. Keep descriptions useful for someone triaging or prioritizing work, not reviewing code.