一键导入
fetch-gitlab-issue
Fetches one or more GitLab issues by ID and displays them in Markdown format. Can also fetch linked issues. Simple, focused on output.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Fetches one or more GitLab issues by ID and displays them in Markdown format. Can also fetch linked issues. Simple, focused on output.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Converts TC files from the docs/wiki repo at {docs_repo}/test-plans/ into Playwright TypeScript test files in the tests repo at {tests_repo}/{test_dir}/. Auto-discovers both repos (sibling → grandparent → ask), reads playwright.config to find the test directory, then asks the user how to handle the branch — write to current branch, create a test/{feature-name} branch from current, or create one from a different source — and writes one spec file per use case sub-folder. Use when generating, writing, or regenerating Playwright test code from the test plan.
Deterministic ABP code generation from a wiki-published Feature Specification, grounded in a prior scan of the repository. Reconnoitres the solution for existing DTOs, entities, AppServices, background workers, hosted services, hubs and event handlers; reconciles them against the Feat Spec into REUSE / UPDATE / CREATE / CONFLICT; writes code only after two user approval gates. Enforces ABP quality gates (no controllers, DomainService over ILocalEventBus cross-aggregate, exception handling, naming, dynamic sorting, select-before-fetch mapping, DeleteAsync soft-delete, ModelBuilder EF Core config, structured logging, implicit tenant scoping). Commands realize as AppService / BackgroundJob / IHostedService / SignalR Hub / EventHandler / CLI per FS Execution-model declaration plus repo evidence — not AppService-only. Migrations remain manual.
Generate a high-level technical Feature Specification (Feat Spec) from Functional Requirement Specification (FRS) issues in a GitLab milestone. Produces an ABP-layered spec in the wiki and a lightweight coordination issue in GitLab.
Audit an existing Functional Requirements Specification (FRS) against the canonical validation contract: structural completeness, Skill Constraint minimums, Self-Review checklist, NFR rubric, Bundling Detection, AC↔FR traceability, glossary resolution, cross-cutting-concerns non-duplication. Reads, never writes. For generating new FRS, use skill:generate-frs. Trigger phrases: review FRS, audit FRS, FRS quality, FRS check, validate spec, FRS findings.
You MUST use this when the user asks to generate Functional Requirements Specifications, break a product/feature/system into business modules, turn meeting notes or rough briefs into formal requirements, or sync requirements to GitLab as milestones and issues. Triggers on keywords: FRS, BRS, functional requirements, business requirements, spec doc, module breakdown, GitLab milestone sync. Fires even when input is rough — the skill infers structure. Accepts prose, React/TS components, and uploaded files. For reviewing existing FRS, use skill:review-frs instead.
You MUST use this when the user asks to review, audit, validate, lint, or check existing Functional Requirements Specifications. Triggers on: reviewing a GitLab FRS issue, auditing a milestone's worth of FRS, validating a pasted FRS, checking an uploaded FRS file (.md/.docx/.pdf), or any phrase like 'is this FRS correct', 'check my FRS', 'audit these requirements', 'validate the FRS'. Fires whether the user wants findings only or findings with proposed fixes. For generating NEW FRS from prose / code / notes, use skill:generate-frs instead.
| name | fetch-gitlab-issue |
| version | 1 |
| description | Fetches one or more GitLab issues by ID and displays them in Markdown format. Can also fetch linked issues. Simple, focused on output. |
| mcp_servers | ["mcp__gitlab"] |
Fetch GitLab issues by ID and show in Markdown.
/get issue 123 from project 3
/show issues 123, 456, 789 in markdown
/fetch issue ABC-456 with links
gitlab_project_idAccept from user:
123123, 456, 789123 (linked) flagmcp__gitlab__get_issue(project_id, issue_iid)
# Issue #{iid}: {title}
**Project:** {project}
**State:** {state} | **Labels:** {labels} | **Assignee:** {@username}
**Weight:** {weight} | **Milestone:** {milestone}
**Created:** {date} | **Updated:** {date}
## Description
{description}
## Linked Issues
#{linked_iid} — {linked_title}
Multiple issues: show separator --- between them.
If user includes "with links" or "linked", for each issue:
mcp__gitlab__list_issue_links(project_id, issue_iid)## Linked Issues sectionSingle issue:
/get issue 42
Outputs:
# Issue #42: Implement user authentication
**Project:** root/acms (ID: 3)
**State:** opened | Labels: user-story, backend | Assignee: @alice
...
Multiple with links:
/show 10, 11, 12 with links
Fetches #10, #11, #12 and all their linked issues, outputs all in Markdown.
Note: No local file writes unless user specifies "save to file".