Transform vague GitHub issues into actionable scope blocks with acceptance criteria.
npx skills add https://github.com/chrisrodz/dotfiles --skill polishing-issues
Please help me install this Agent Skill. Skill: polishing-issues Source: https://github.com/chrisrodz/dotfiles/tree/main/ai/skills/polishing-issues Command: npx skills add https://github.com/chrisrodz/dotfiles --skill polishing-issues
Turn a vague or incomplete GitHub issue into a concise, executable spec that a coding agent can implement without back-and-forth.
Draft a concise scope block for the given issue and append it to the issue body
High-intent search queries and answers about installing and using this skill.
To turn a vague GitHub issue into an actionable spec, the Skill extracts context and generates a self-contained scope block with explicit touchpoints, acceptance criteria, and a task breakdown ready for immediate work.
The best way to add acceptance criteria and validation is by generating a template-driven scope block that includes API/data changes, edge cases, and a task breakdown with explicit inputs, outputs, and validation parameters.
You create a task breakdown by transforming the issue into a structured scope block, which divides the work into small, verifiable tasks complete with required modification touchpoints and validation parameters.
Yes, you can automatically draft a focused scope block that mirrors the issue structure, integrating assumptions, goals, and modification touchpoints into a ready-to-edit template appended to the issue body.
Yes, this approach works for automated coding by producing a concise, executable spec that handles issues lacking clear scope, ensuring a coding agent can implement the work without back-and-forth clarification.
GYF0311Transform unstructured article dumps into structured pages with summaries and quotes.
kangmominConvert API work requests into actionable Technical Specs through guided questioning and codebase exploration.
tatsushige-iConvert conversation context into a GitHub issue with generated title, body, and labels.
iAziz786Draft GitHub issues with structured spec templates for problems, criteria, and dependencies.
