mps-bugfix

Structured MPS bugfix workflow driven by a YouTrack issue ID — preflight tool checks, version/branch derivation, parallel-agent problem analysis, solution design, branch creation, implementation, review, and YouTrack updates. Use when the user invokes "/bugfix", asks to "fix a bug", "work on a bug", "investigate an issue", or provides a YouTrack issue ID.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, clearly sequenced multi-phase workflow with strong validation gates and progressive-disclosure signaling. Its main weakness is that the detailed reference files it points to are missing from the bundle, leaving some actionability and disclosure promises unfulfilled.

Suggestions

Ship the referenced `references/*.md` files (issue-fields, platform-prompt, version-prompt, branch-naming, explore-prompts, root-cause-template, review-checklist, completion-comment) so the deferred prompts, templates, and branch-naming table are actually available.

De-duplicate the approval-gate and 'prefer the source of truth' directives — state each once in Critical Directives and reference it from Phase 4/5 instead of repeating the full text.

Add a couple of natural trigger variants (e.g. "report a bug", "regression", "defect") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Conciseness	The body is a lean workflow outline that assumes Claude's competence about git, YouTrack, and MPS, but the approval-gate and 'prefer fixing the source of truth' directives are repeated 2–3 times across Critical Directives, Phase 4, and Phase 5.	4 / 5
Actionability	Provides real executable commands (`git branch -r --list 'origin/20'`, `git checkout`, named `mcp_idea_` / `get_issue` / `update_issue` tools), but key prompts, templates, and the branch-naming table are deferred to `references/*.md` files that are not present in the bundle.	4 / 5
Workflow Clarity	Phases 0–7 are clearly sequenced with explicit validation checkpoints (Phase 0 preflight stops on missing tools, per-change validation), approval gates before implementation, and a review fix-loop; the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	In-body signaling is exemplary with a dedicated Reference Index and one-level-deep references, but the referenced `references/*.md` bundle files do not exist on disk, so the cross-file structure is promised but unrealized.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is excellent: it concisely states a concrete multi-step capability and pairs it with explicit, natural trigger phrases anchored to a specific YouTrack-driven niche. Only minor trigger-term variants are missing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — preflight tool checks, version/branch derivation, parallel-agent problem analysis, solution design, branch creation, implementation, review, and YouTrack updates — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Clearly answers both 'what' (structured MPS bugfix workflow with enumerated phases) and 'when' (explicit "Use when..." clause with concrete trigger phrases), matching the anchor example closely.	5 / 5
Trigger Term Quality	Strong natural triggers are present ("/bugfix", "fix a bug", "work on a bug", "investigate an issue", YouTrack issue ID), but a few common variants like "report a bug", "regression", or "defect" are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (MPS bugfix workflow driven by a YouTrack issue ID) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 16 missing	Warning

	Total	14 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/mps-bugfix/SKILL.md
Commit: c74b207

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.