Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

jira-fetch

Sterne4

Forks0

Aktualisiert17. Juni 2026 um 06:41

Fetch a Jira ticket and write its full structured content to disk (.jira/<KEY>/). Extracts all standard fields, all custom fields present on the issue, attachments, and linked assets (Figma URLs, images, files). Use this skill whenever the user mentions a Jira ticket key (e.g. SHOP-123, LBE-456, LCA-789), pastes a Jira URL (atlassian.net/browse/...), says "fetch the ticket", "pull the Jira issue", "get the ticket", "show me the ticket", "read the Jira", or needs to start working on a ticket. Also triggers when the user mentions ticket context like "the acceptance criteria", "the business rules from the ticket", "the Figma from the ticket", "what does the ticket say about X", or any phrase that implies reading a Jira issue.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

ClubMediterranee

ClubMediterranee/ai-core

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	jira-fetch
description	Fetch a Jira ticket and write its full structured content to disk (.jira/<KEY>/). Extracts all standard fields, all custom fields present on the issue, attachments, and linked assets (Figma URLs, images, files). Use this skill whenever the user mentions a Jira ticket key (e.g. SHOP-123, LBE-456, LCA-789), pastes a Jira URL (atlassian.net/browse/...), says "fetch the ticket", "pull the Jira issue", "get the ticket", "show me the ticket", "read the Jira", or needs to start working on a ticket. Also triggers when the user mentions ticket context like "the acceptance criteria", "the business rules from the ticket", "the Figma from the ticket", "what does the ticket say about X", or any phrase that implies reading a Jira issue.
allowed-tools	Bash, Read, Write
version	1.0.0
changelog	[{"version":"1.0.0","date":"2026-06-12T00:00:00.000Z","changes":["Initial release"]}]
created-at	"2026-06-12T00:00:00.000Z"
created-by	Raphaël Moisset <raphael.moisset@clubmed.com>
context	fork

Jira Fetch

Fetch a Jira ticket and persist its full structured content to .jira/<KEY>/ in the working directory. Extracts all fields — standard and custom — plus aggregates all linked assets (Figma URLs, image attachments, file attachments).

When to run

Whenever a ticket key or Jira URL appears in context and the user needs its content to start work, review acceptance criteria, find a Figma link, or understand requirements.

Step 1 — Resolve the ticket key

Extract the key from whatever the user provided:

Bare key: SHOP-2124 → use as-is
URL: https://clubmed.atlassian.net/browse/SHOP-2124 → extract SHOP-2124

Step 2 — Fetch the raw issue

Choose the method based on what's available in the environment:

MCP method (preferred when `mcpjiraget_issue` is available)

# Call the MCP tool, save raw response
mcp__jira__get_issue issueKey="<KEY>"

Save the full JSON response to /tmp/jira-<KEY>.json.

CLI method (fallback)

JIRA_KEY="<KEY>"
jira issue view "$JIRA_KEY" --raw > "/tmp/jira-${JIRA_KEY}.json"

If neither works, ask the user to paste the ticket content manually and write it verbatim to .jira/<KEY>/raw.txt.

Step 3 — Extract and render all fields

Run the bundled extraction script:

python3 "$(dirname "$0")/scripts/extract-jira-fields.py" "/tmp/jira-<KEY>.json" --output-dir ".jira/<KEY>"

The script:

Renders every field present in fields (not just a hardcoded list)
Detects and renders ADF (Atlassian Document Format) fields as Markdown
Scans all rendered text for Figma URLs and deduplicates them
Downloads or lists all file attachments into .jira/<KEY>/attachments/
Writes .jira/<KEY>/ticket.md — the main structured output

Step 4 — Output location

By default, all output goes to .jira/<KEY>/:

.jira/
└── SHOP-2124/
    ├── ticket.md          ← structured Markdown of the full ticket
    ├── attachments/       ← downloaded binary files (images, PDFs, etc.)
    └── raw.json           ← copy of the raw API response for debugging

If the user requests a specific output location or format in their prompt, honour that instead. Examples:

"save to /tmp/SHOP-2124.md" → write there
"just show me the ticket" → print ticket.md to the conversation, skip the file write
"paste the business rules" → print only the BUSINESS RULES section

Step 5 — Confirm to the user

After writing files, report:

Fetched SHOP-2124: <summary>
Output: .jira/SHOP-2124/ticket.md
Figma URLs found: <N>
Attachments: <N> files

If there are Figma URLs, list them explicitly so the user can see them at a glance.

Known Club Med custom fields

These fields are common in Club Med Jira projects. The script will still extract any custom field present on the issue — this table is just reference context for how to label them in the output:

Field ID	Label
`customfield_11553`	User Story
`customfield_11554`	Business Rules
`customfield_11556`	QA Scenarios
`customfield_12207`	API Resources
`customfield_12208`	Design Notes
`customfield_11563`	Figma URL
`customfield_11547`	DOR

For fields not in this table, use the name from the field schema or fall back to the raw field ID as the section heading.

Error handling

Situation	Action
Auth error or 401	Print `ERROR: auth failed — run \`jira login` or check MCP credentials`
Ticket not found (404)	Print `ERROR: <KEY> not found — verify the key and project access`
ADF rendering fails	Fall back to raw JSON string for that field, note the fallback in output
Attachment download fails	Log the attachment name and URL in ticket.md under a "Failed downloads" note

Mehr aus diesem Repository

gleiches Repository

git-push-branch

ClubMediterranee/ai-core

Push the current branch to the remote under a speaking branch name derived from the last conventional commit (<type>/<scope>-<description>). Use when the user asks to push their branch, publish their work, push before opening a PR, or push with a meaningful branch name. Hard guard: NEVER pushes the default branch (detected dynamically from origin/HEAD — main, develop, etc.) — if HEAD is on it, a speaking feature branch is carved and switched to first. Sets upstream with -u. Triggers on: "push", "push my branch", "push this", "publish my branch", "push with a good branch name", "push before PR".

2026-07-164

github-publish

ClubMediterranee/ai-core

End-to-end "send my work to GitHub": commit the current changes as a Conventional Commit, rebase onto the default branch, push under a speaking branch name, and open a GitHub pull request — in one flow. Use when the user wants to ship their work, send changes to GitHub, open a PR from their current changes, "commit push and PR", finalize a feature, or go from dirty working tree to an open PR. Composes the git-commit, git-rebase-branch, git-push-branch, and github-open-pr skills. Absolute invariant: NEVER pushes to the default branch (main, develop, etc.) — always a feature branch and a PR. Triggers on: "send to github", "ship it", "ship this", "open a PR for my changes", "commit push and open a PR", "finalize this feature", "create a PR from my work", "/github-publish".

2026-07-164

github-update

ClubMediterranee/ai-core

Update the current branch with its remote counterpart using a rebase (git pull --rebase), keeping history linear and avoiding merge commits. Fetches the branch upstream, replays local commits on top, and handles conflicts (safe automatic resolution for trivial overlaps, asks the user to arbitrate genuine logic conflicts). Use when the user asks to pull with rebase, get the latest remote commits on their branch, update/sync the current branch with its remote, resolve a "your branch is behind" state without a merge commit, or catch up before continuing work. Refuses to run on a dirty working tree (stops and asks to commit or stash first), never force-pushes, never touches git config, and prefers `git rebase --abort` over leaving a broken state. Triggers on: "pull rebase", "git pull --rebase", "get the latest commits", "update my branch from remote", "sync with the remote", "my branch is behind origin", "catch up before I continue".

2026-07-164

e2e-test-generator

ClubMediterranee/ai-core

Generate robust Playwright + TypeScript end-to-end tests for Club Med B2C sites. Use when the user asks to write E2E tests, add coverage for a user journey, or harden a flaky suite. Qualifies the test intent (including reading the repo's docs/ for PRDs and glossaries), then orchestrates five phases — ground selectors on the live site, plan scenarios, write from the grounded contract reusing existing code, prove non-flakiness by repeated cross-browser runs, and review with independent critics.

2026-07-154

git-rebase-branch

ClubMediterranee/ai-core

Rebase the current branch onto the latest default branch (detected dynamically from the remote — main, develop, or whatever origin/HEAD points to), safely. Use when the user asks to rebase, update their branch with the default branch, sync with the default branch, resolve a "branch is behind" state, or before pushing/opening a PR. Protects the default branch: if HEAD is on it, it carves a speaking feature branch from the last commit FIRST and never rebases the default branch itself. Attempts safe automatic conflict resolution and only asks the user to arbitrate genuine conflicts. Triggers on: "rebase", "rebase on main", "update my branch", "sync with main", "my branch is behind", "rebase before pushing".

2026-07-104

github-authentication

ClubMediterranee/ai-core

Generates, validates, and persists a GitHub personal access token (PAT) to .claude/settings.local.json (Claude Code local settings). Use this skill whenever a GitHub token is needed, missing, expired, or must be refreshed — before any task that calls the GitHub API or connects the GitHub MCP server. Triggers on: "generate github token", "create github token", "set up github token", "update github token", "GITHUB_TOKEN missing", "GITHUB_TOKEN not set", "GITHUB_TOKEN expired", "github token invalid", "github authentication", "connect github mcp", "configure github access", or any task that requires GitHub API access and the token is absent or invalid. Works by checking for an existing valid token first, then manual browser login (the primary path — GitHub enforces 2FA), with optional best-effort auto-login if GITHUB_USERNAME/GITHUB_PASSWORD are available. Token is stored in .claude/settings.local.json and auto-injected by Claude Code into every shell session. Browser automation uses the Playwright MCP.

2026-07-104

name	jira-fetch
description	Fetch a Jira ticket and write its full structured content to disk (.jira/<KEY>/). Extracts all standard fields, all custom fields present on the issue, attachments, and linked assets (Figma URLs, images, files). Use this skill whenever the user mentions a Jira ticket key (e.g. SHOP-123, LBE-456, LCA-789), pastes a Jira URL (atlassian.net/browse/...), says "fetch the ticket", "pull the Jira issue", "get the ticket", "show me the ticket", "read the Jira", or needs to start working on a ticket. Also triggers when the user mentions ticket context like "the acceptance criteria", "the business rules from the ticket", "the Figma from the ticket", "what does the ticket say about X", or any phrase that implies reading a Jira issue.
allowed-tools	Bash, Read, Write
version	1.0.0
changelog	[{"version":"1.0.0","date":"2026-06-12T00:00:00.000Z","changes":["Initial release"]}]
created-at	"2026-06-12T00:00:00.000Z"
created-by	Raphaël Moisset <raphael.moisset@clubmed.com>
context	fork

Jira Fetch

When to run

Whenever a ticket key or Jira URL appears in context and the user needs its content to start work, review acceptance criteria, find a Figma link, or understand requirements.

Step 1 — Resolve the ticket key

Extract the key from whatever the user provided:

Bare key: SHOP-2124 → use as-is
URL: https://clubmed.atlassian.net/browse/SHOP-2124 → extract SHOP-2124

Step 2 — Fetch the raw issue

Choose the method based on what's available in the environment:

MCP method (preferred when `mcpjiraget_issue` is available)

# Call the MCP tool, save raw response
mcp__jira__get_issue issueKey="<KEY>"

Save the full JSON response to /tmp/jira-<KEY>.json.

CLI method (fallback)

JIRA_KEY="<KEY>"
jira issue view "$JIRA_KEY" --raw > "/tmp/jira-${JIRA_KEY}.json"

If neither works, ask the user to paste the ticket content manually and write it verbatim to .jira/<KEY>/raw.txt.

Step 3 — Extract and render all fields

Run the bundled extraction script:

python3 "$(dirname "$0")/scripts/extract-jira-fields.py" "/tmp/jira-<KEY>.json" --output-dir ".jira/<KEY>"

The script:

Renders every field present in fields (not just a hardcoded list)
Detects and renders ADF (Atlassian Document Format) fields as Markdown
Scans all rendered text for Figma URLs and deduplicates them
Downloads or lists all file attachments into .jira/<KEY>/attachments/
Writes .jira/<KEY>/ticket.md — the main structured output

Step 4 — Output location

By default, all output goes to .jira/<KEY>/:

.jira/
└── SHOP-2124/
    ├── ticket.md          ← structured Markdown of the full ticket
    ├── attachments/       ← downloaded binary files (images, PDFs, etc.)
    └── raw.json           ← copy of the raw API response for debugging

If the user requests a specific output location or format in their prompt, honour that instead. Examples:

"save to /tmp/SHOP-2124.md" → write there
"just show me the ticket" → print ticket.md to the conversation, skip the file write
"paste the business rules" → print only the BUSINESS RULES section

Step 5 — Confirm to the user

After writing files, report:

Fetched SHOP-2124: <summary>
Output: .jira/SHOP-2124/ticket.md
Figma URLs found: <N>
Attachments: <N> files

If there are Figma URLs, list them explicitly so the user can see them at a glance.

Known Club Med custom fields

These fields are common in Club Med Jira projects. The script will still extract any custom field present on the issue — this table is just reference context for how to label them in the output:

Field ID	Label
`customfield_11553`	User Story
`customfield_11554`	Business Rules
`customfield_11556`	QA Scenarios
`customfield_12207`	API Resources
`customfield_12208`	Design Notes
`customfield_11563`	Figma URL
`customfield_11547`	DOR

For fields not in this table, use the name from the field schema or fall back to the raw field ID as the section heading.

Error handling

Situation	Action
Auth error or 401	Print `ERROR: auth failed — run \`jira login` or check MCP credentials`
Ticket not found (404)	Print `ERROR: <KEY> not found — verify the key and project access`
ADF rendering fails	Fall back to raw JSON string for that field, note the fallback in output
Attachment download fails	Log the attachment name and URL in ticket.md under a "Failed downloads" note

jira-fetch

Jira Fetch

When to run

Step 1 — Resolve the ticket key

Step 2 — Fetch the raw issue

MCP method (preferred when mcp__jira__get_issue is available)

CLI method (fallback)

Step 3 — Extract and render all fields

Step 4 — Output location

Step 5 — Confirm to the user

Known Club Med custom fields

Error handling

Mehr aus diesem Repository

Mehr aus diesem Repository

Jira Fetch

When to run

Step 1 — Resolve the ticket key

Step 2 — Fetch the raw issue

MCP method (preferred when mcp__jira__get_issue is available)

CLI method (fallback)

Step 3 — Extract and render all fields

Step 4 — Output location

Step 5 — Confirm to the user

Known Club Med custom fields

Error handling

MCP method (preferred when `mcpjiraget_issue` is available)

MCP method (preferred when `mcpjiraget_issue` is available)