ss-agile-polishing-an-issue

Polishes a GitHub pull-request diff while preserving behavior and checking acceptance criteria.

Updated May 19, 2026

Search Tags:#pull request #github #acceptance criteria #autonomous agent #error messages #refactoring safety #code polishing

Ready to run

npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-agile-polishing-an-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ss-agile-polishing-an-issue
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/agile-ralph-loop/ss-agile-polishing-an-issue
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-agile-polishing-an-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It improves an implementer’s GitHub issue PR by making the changed code clearer, safer to read, and less messy—without altering intended behavior or blocking the merge.

Core Features & Use Cases

Conservative polishing pass: improves naming, comments, structure within the diff, formatting/lint, and test descriptions while keeping behavior the same.
Dead-code and message cleanup: removes unused imports/variables and stale TODOs within scope, and upgrades unhelpful error messages without changing when errors trigger.
Acceptance-criteria sanity check (info only): flags possibly-unmet criteria when they are plainly missing from the diff, but never vetoes or blocks merging.

Quick Start

Use ss-agile-polishing-an-issue when dispatched as a subagent after an implementer reports “done” on a GitHub issue, then return a structured polishing report to the coordinator.

Frequently Asked Questions about ss-agile-polishing-an-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I polish a pull request diff without changing observable behavior?▼

Polishing a pull request diff without changing behavior involves improving naming, comments, structure, and error messages within the changed code. It removes dead code and stale TODOs while maintaining strict non-interactive operation and reverting automatically if tests fail.

What is an autonomous subagent for code polishing on GitHub issues?▼

An autonomous subagent for code polishing is a non-interactive process dispatched after implementation to clean up a GitHub issue PR. It performs a diff-scoped cleanup, upgrades unhelpful error messages, and checks acceptance criteria without vetoing merges.

Can I use an autonomous agent to check acceptance criteria without blocking a PR merge?▼

Yes, you can use an autonomous agent to check acceptance criteria without blocking a merge by operating in an info-only flagging mode. The agent identifies possibly unmet criteria plainly missing from the diff but holds zero merge veto power.

How do I safely clean up dead code and improve error messages in a GitHub PR?▼

To safely clean up dead code and improve error messages in a GitHub PR, apply a conservative polishing pass limited strictly to the diff scope. Remove unused imports and variables, upgrade unhelpful error messages without changing when errors trigger, and revert on test failure.

What are the limitations of using an autonomous agent for refactoring safety in pull requests?▼

Limitations of using an autonomous agent for refactoring safety include strict non-interactive operation, meaning it never asks questions, and conservative scope limits restricting changes to the diff. It also lacks merge veto power and must revert changes if tests fail.