Score GitHub issues with a rubric and draft structured rewrites with acceptance criteria.
npx skills add https://github.com/ahlerjam/mmp --skill ticket-improvement
Please help me install this Agent Skill. Skill: ticket-improvement Source: https://github.com/ahlerjam/mmp/tree/main/skills/ticket-improvement Command: npx skills add https://github.com/ahlerjam/mmp --skill ticket-improvement
It helps you upgrade low-quality or underspecified GitHub tickets into clearer, testable issue descriptions without scope creep, by scoring issues and drafting structured improvements for per-ticket approval.
gh CLI; in local mode it writes final files for downstream phases.Ask mmp to improve the tickets in your selected milestone by running the improve-tickets workflow and approving each ticket’s diff before applying changes.
High-intent search queries and answers about installing and using this skill.
To rewrite vague GitHub issues, this Skill scores each ticket with a quality rubric and drafts a structured, scope-safe rewrite with acceptance criteria. It enforces hard rules like preserving references and never inventing criteria, then requires per-ticket diff approval before applying changes.
Race detection for live GitHub issue edits works by re-fetching the ticket and comparing a hash before applying changes. If the hash matches the previewed state, it posts a backup comment and applies approved edits through the GitHub CLI to prevent overwriting concurrent modifications.
Yes, you can triage and improve tickets across a milestone using the GitHub CLI. The Skill applies to milestone-based ticket triage by scoring each issue, drafting improvements, and applying approved diffs sequentially while respecting skip labels to exclude specific tickets.
The best way to prevent scope creep when improving GitHub tickets is using a dedicated improver that drafts acceptance-criteria-focused rewrites while enforcing hard rules. It preserves existing references and never invents acceptance criteria that were not implied by the original issue.
Yes, you need to approve each ticket's diff before changes are applied. The Skill requires per-ticket diff preview and hard approval gates, ensuring you review every structured rewrite before it is pushed to GitHub via the CLI or written locally for downstream phases.
Some GitHub issues are skipped during ticket improvement because the Skill respects skip labels configured on the tickets. If an issue is classified as GOOD by the quality rubric or carries a skip label, it focuses work only where improvement is likely beneficial.
NSEvteevAudit GitHub issues for title, labels, milestone, and body conformance.
scute-shManage GitHub issues from comprehension through PR creation and CI verification.
ev3rlitConvert plain-text task lists into Mermaid Kanban diagrams with metadata.
bejranondaDetect JavaScript errors and collect browser diagnostics from web pages.