jira
Conventions for creating and managing Jira tickets
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Conventions for creating and managing Jira tickets
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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.