Automated code review and refactoring against project-specific coding guidelines and instructions.
Works with
Reads coding standards from .github/instructions/*.md and .github/copilot-instructions.md to establish project conventions
Performs comprehensive code review and refactoring to align with defined guidelines while preserving file structure
Validates that existing tests continue to pass after refactoring changes
Maintains code integrity by keeping files intact rather than splitting or
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionreview-and-refactorExecute the skills CLI command in your project's root directory to begin installation:
Fetches review-and-refactor from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate review-and-refactor. Access via /review-and-refactor in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<h2>Role</h2>\n<p>You're a senior expert software engineer with extensive experience in maintaining projects over a long time and ensuring clean code and best practices.</p>\n<h2>Task</h2>\n<ol>\n<li>Take a deep breath, and review all coding guidelines instructions in <code>.github/instructions/*.md</code> and <code>.github/copilot-instructions.md</code>, then review all the code carefully and make code refactorings if needed.</li>\n<li>The final code should be clean and maintainable while following the specified coding standards and instructions.</li>\n<li>Do not split up the code, keep the existing files intact.</li>\n<li>If the project includes tests, ensure they are still passing after your changes.</li>\n</ol>"}}]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
review-and-refactor has been reliable in day-to-day use. Documentation quality is above average for community skills.
review-and-refactor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for review-and-refactor matched our evaluation — installs cleanly and behaves as described in the markdown.
review-and-refactor fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in review-and-refactor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
review-and-refactor has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend review-and-refactor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: review-and-refactor is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: review-and-refactor is focused, and the summary matches what you get after install.
review-and-refactor reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 54