OpenParable
Skip to content
← Back to skills

Polishing Issues

Productivity
polishing-issues

Polishing Issues is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Make a GitHub issue self-contained for a single feature/fix so any coding agent can execute it without back-and-forth. Focus on scope, file touchpoints, acceptance criteria, and validation.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/polishing-issues/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/polishing-issues, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Polish Issue Scope (Single Feature)

Goal: turn one issue into a complete, actionable spec for a single feature or fix. Keep it concise, technical, and executable without follow-up questions.

Use When

  • Issue is missing scope, acceptance criteria, or validation.
  • Issue references a feature/fix but lacks file touchpoints or constraints.
  • You need an execution-ready issue for a coding agent.

Do Not Use

  • Multi-epic planning or multi-sprint roadmaps.
  • Full product/spec interviews (use the interview skill for that).

Workflow

  1. Fetch the issue
gh issue view <number> --repo <owner/repo> --json title,body,labels,state,comments
  1. Scan the codebase
  • Locate related files or patterns with rg.
  • Identify likely files to modify or create.
  • Note constraints (existing APIs, data models, UI patterns, tests).
  1. Resolve blockers
  • Ask all blocking questions for the issue.
  • If not blocking, confirm assumptions with user before proceeding.
  1. Draft a concise scope block
  • Keep to bullets, no fluff.
  • Provide enough context to implement without follow-up.
  1. Show preview and confirm
  • Present exact markdown to append.
  • Wait for explicit approval before editing the issue.
  1. Update the issue
CURRENT_BODY=$(gh issue view <number> --repo <owner/repo> --json body -q .body)

gh issue edit <number> --repo <owner/repo> --body "$CURRENT_BODY

---

[scope block here]"

Scope Block Template

## Scope

**Summary**
- <1-2 sentence summary of the change>

**Assumptions**
- <explicit assumptions or defaults made>

**Goals**
- <what must be true when done>

**Non-goals**
- <explicitly out of scope>

**User impact**
- <who is affected and how>

**Touchpoints**
- Modify: `path/to/file.ts` - <why>
- Create: `path/to/new-file.ts` - <why>

**API/data changes** (if any)
- <schema, endpoints, migrations>

**Edge cases**
- <list>

**Acceptance criteria**
- [ ] <testable outcome>
- [ ] <testable outcome>

**Validation**
- Tests: `<command or file>`
- Manual: <steps>

**Task breakdown** (atomic, commit-ready)
1. <task title>
   - Inputs: <files/data/flags>
   - Outputs: <artifacts/changes>
   - Steps: <1-3 concrete steps>
   - Validation: <test or check>
   - Complexity: <1-10>
2. <task title>
   - Inputs: <files/data/flags>
   - Outputs: <artifacts/changes>
   - Steps: <1-3 concrete steps>
   - Validation: <test or check>
   - Complexity: <1-10>

**Dependencies / risks**
- <libs, feature flags, env vars, rollout concerns>

Rules

  • Prefer explicit file paths and code locations.
  • Each task must be small and independently verifiable.
  • Each task must include inputs/outputs and 1-3 concrete steps.
  • Complexity is a 1-10 estimate; split tasks above 7.
  • If there are multiple viable approaches, list them briefly and pick a recommendation unless the choice blocks implementation.
  • Avoid long narrative; keep it scannable.