القائمة
Creates a Jira ticket from context in the current conversation or codebase. Use when the user wants to log a bug, feature request, task, or spike in Jira.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Post or update a comment on a Linear ticket using the Linear MCP server. Accepts a ticket ID (e.g. ENG-123), a Linear ticket URL, or a direct link to an existing comment. Works for both human-authored comments and agent-generated summaries.
Creates a Linear document (the Documents feature, distinct from issues/projects) from context in the current conversation, a plan, or a file. Use when the user wants to write up a doc, spec, RFC, or notes page in Linear and attach it to a team, project, initiative, cycle, or issue.
Used to run githooks, perform code & plan reviews with expert critics, and commit/push verified changes
Creates a Linear project under an initiative from a draft list of tickets, clarifies ambiguity with the human, then creates the project and each ticket via /create-linear-ticket. Use when the user wants to stand up a new project in Linear from a plan, doc, or ticket list.
Used to build and execute an approved implementation plan by spinning up agents
Used to gather requirements, clarify scope, and create implementation plans for new feature requests or bug fixes
| name | create-jira-ticket |
| description | Creates a Jira ticket from context in the current conversation or codebase. Use when the user wants to log a bug, feature request, task, or spike in Jira. |
Collect information about the ticket from whatever is available — in order of priority:
/create-jira-ticket fix the login redirect bug)If none of the above provide enough signal, ask the human to describe the issue or feature in plain text.
Use the Atlassian connector to list accessible Atlassian sites and available Jira projects. If the connector is not configured, prompt the human to set it up before proceeding.
If the human has previously used a project in this conversation, default to that. Otherwise ask the human to pick a project from the list.
Use the Atlassian connector to fetch valid issue types for the selected project.
Based on the context, suggest the most appropriate type (Bug, Story, Task, Spike, etc.) and confirm with the human if it's not obvious.
Construct a draft with the following fields — infer as much as possible from context:
_Filed by {your identity} on behalf of @<github-or-jira-handle>._
## Context
<what is happening / what needs to be done>
## Expected behavior / Goal
<what should happen>
## Acceptance Criteria
- <criterion 1>
- <criterion 2>
## Notes
<any relevant links, code references, error messages. Do not attribute to "Claude Code" — attribute to your identity as defined in CLAUDE.md.>
Use the Atlassian connector to check which fields are required for the chosen issue type and project.
Format the description as Atlassian Document Format (ADF) — not markdown. Use ADF paragraph, bulletList, and heading nodes as appropriate.
Present the full draft clearly. Remind the human that this will post codebase context (code snippets, error messages, etc.) to Jira — confirm they're comfortable with that before proceeding. Do not create the ticket until explicitly approved.
Once approved, use the Atlassian connector to create the ticket.
Report back:
PROJ-123)