Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Ask whether they have considered other options, and present other options to them.
Interview the user about the implementation. Be extremely detailed and thorough.
Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.
Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."
Create a GitHub issue with the refactor plan. Use the following template for the issue description:
The problem that the developer is facing, from the developer's perspective.
The solution to the problem, from the developer's perspective.
A LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this refactor.
Any further notes about the refactor.
</refactor-plan-template>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use Cursor's browser aria snapshots to audit a page for accessibility issues — missing labels, broken tab order, contrast, and ARIA misuse.
The English summary is being prepared. Showing the original description.
Add PostHog analytics to a web application, including event tracking, page views, feature flags, and session replay.
The English summary is being prepared. Showing the original description.
Generate OpenAPI/Swagger documentation for an API, including endpoint schemas, request/response types, and interactive docs UI.
The English summary is being prepared. Showing the original description.
Add authentication to a web application using NextAuth.js (Auth.js), including OAuth providers, session management, and protected routes.
The English summary is being prepared. Showing the original description.
Dockerize an application with a production-ready Dockerfile, docker-compose setup, and .dockerignore.
The English summary is being prepared. Showing the original description.
Set up Playwright end-to-end testing in a project, including test configuration, example tests, and CI integration.
The English summary is being prepared. Showing the original description.