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 页面并帮你完成安装。
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.