원클릭으로 Manus에서 모든 스킬 실행

jira-ticket

스타3

포크1

업데이트2026년 6월 15일 05:15

Prepare Jira create, comment, and safe-update payloads with safe dry-run fallback. Use with /jira-ticket when work tracking is requested.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

damian87x

damian87x/oh-my-copilot

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Jira Ticket

Use /jira-ticket when work tracking is requested.

When to use

A plan or completed work needs a Jira ticket
You need to comment on or update an existing ticket
The user wants a ticket draft without actually creating it

Operations

Create

Build from an approved plan or implementation slice (a plan file or markdown)
Include: Summary, Description, Acceptance Criteria
Render the payload with omp jira render <plan-file> — this never writes to Jira. To create/comment/update, run omp jira apply <plan-file-or-ticket-key>, which defaults to dry-run and only writes when Jira is configured with JIRA_MODE=live, the user has explicitly confirmed, and the CLI has explicit body/field support for the operation you need.

Comment

Add implementation evidence, verification results, or status updates
Format for readability (use Jira wiki markup, not Markdown)
Draft the comment payload and preview via dry-run only; do not run live comment writes from this skill until the CLI accepts an explicit comment body/body file.

Safe update

Only update known simple fields (summary, description, labels)
Draft update fields and preview via dry-run only; do not run live update writes from this skill until the CLI accepts explicit update fields.
Do not guess transitions, issue links, project keys, or secrets

Rules

Always preview with omp jira render or omp jira apply … --dry-run (the default); live writes require explicit user confirmation plus CLI support for the exact payload being written
If Jira config is missing, the commands stay in dry-run and print the payload — never fail silently
Do not guess project keys, transitions, or credentials
Keep acceptance criteria testable and specific
Include file paths and evidence when commenting with implementation details

Output

Operation — create / comment / update
Target — ticket key or "new"
Payload — the Jira-formatted content
Human action — what the user needs to do (e.g. "paste into Jira" if dry-run)

이 저장소의 다른 Skills

같은 저장소

skill-bench

damian87x/oh-my-copilot

Use when a user wants to compare an arbitrary skill or path across models, quality, cost, latency, or routing.

2026-07-173

history-analyze

damian87x/oh-my-copilot

Analyze actual local Copilot skill activations without reading conversation content.

2026-07-163

wayfinder

damian87x/oh-my-copilot

Plan work too big for one agent session as a shared map of decision tickets on GitHub Issues or Jira, then resolve them one at a time until the route is clear. Use with /wayfinder when the user says "plan something too big for one session", "chart a map", "wayfind", "work the map", or "decision tickets". Always confirm tracker (GitHub vs Jira) and destination before writing. Adapted from mattpocock/skills wayfinder (MIT).

2026-07-163

handoff

damian87x/oh-my-copilot

Create or resume a task handoff so a fresh agent can continue unfinished work. Persist via omp handoff CLI (never write handoff files yourself). Use when the user says /handoff, wants to pause mid-task, or resume prior work.

2026-07-153

ralph

damian87x/oh-my-copilot

Single-owner execute-fix-verify loop for one clear task. Use with /ralph when one agent should keep going until evidence or blocker.

2026-07-053

ultraqa

damian87x/oh-my-copilot

Adversarial QA pass that tests behavior, failures, and regressions. Use with /ultraqa after implementation when shallow checks are not enough.

2026-07-053

Jira Ticket

Use /jira-ticket when work tracking is requested.

When to use

A plan or completed work needs a Jira ticket

You need to comment on or update an existing ticket

The user wants a ticket draft without actually creating it

Operations

Create

Build from an approved plan or implementation slice (a plan file or markdown)

Include: Summary, Description, Acceptance Criteria

Render the payload with omp jira render <plan-file> — this never writes to Jira. To create/comment/update, run omp jira apply <plan-file-or-ticket-key>, which defaults to dry-run and only writes when Jira is configured with JIRA_MODE=live, the user has explicitly confirmed, and the CLI has explicit body/field support for the operation you need.

Comment

Add implementation evidence, verification results, or status updates

Format for readability (use Jira wiki markup, not Markdown)

Draft the comment payload and preview via dry-run only; do not run live comment writes from this skill until the CLI accepts an explicit comment body/body file.

Safe update

Only update known simple fields (summary, description, labels)

Draft update fields and preview via dry-run only; do not run live update writes from this skill until the CLI accepts explicit update fields.

Do not guess transitions, issue links, project keys, or secrets

Rules

Always preview with omp jira render or omp jira apply … --dry-run (the default); live writes require explicit user confirmation plus CLI support for the exact payload being written

If Jira config is missing, the commands stay in dry-run and print the payload — never fail silently

Do not guess project keys, transitions, or credentials

Keep acceptance criteria testable and specific

Include file paths and evidence when commenting with implementation details

Output

Operation — create / comment / update

Target — ticket key or "new"

Payload — the Jira-formatted content

Human action — what the user needs to do (e.g. "paste into Jira" if dry-run)

name	jira-ticket
description	Prepare Jira create, comment, and safe-update payloads with safe dry-run fallback. Use with /jira-ticket when work tracking is requested.