SWE Refactor Opportunities
Skill Verified ActiveReviews a repository and returns a short, best-first backlog of small, low-risk refactor tickets with clear write boundaries and validation paths. Use when a user says `find refactor opportunities`, `what small cleanup tickets should we hand to agents`, `give me parallelizable refactors`, or asks for narrow maintainability wins in an existing repo. Do NOT use for a broad architecture redesign, style-only cleanup sweep, or bug hunt focused on functional regressions.
To streamline code maintenance by providing developers with a focused backlog of small, parallelizable refactor tickets, improving code quality and reducing cognitive load.
Features
- Generates a shortlist of small refactor tickets
- Prioritizes tickets by leverage, safety, and clarity
- Considers repository structure and patterns
- Tailors suggestions based on recent contribution history
- Clearly defines write boundaries and validation paths
Use Cases
- Finding narrow refactors for immediate assignment
- Identifying parallelizable tasks for agent teams
- Getting actionable maintainability wins in an existing repo
- Brainstorming small cleanup tasks instead of broad architectural changes
Non-Goals
- Broad architecture redesigns
- Style-only cleanup sweeps
- Bug hunting focused on functional regressions
- Generating vague or unassignable advice
Workflow
- Inspect the repository for refactor surfaces
- Identify repeated code paths, large surfaces, and confusing conditionals
- Filter for small, safe, and behavior-preserving refactor candidates
- Tailor suggestions based on available contribution history
- Rank and write ticket-shaped suggestions with detailed fields
Practices
- Code quality
- Maintainability
- Developer productivity
Prerequisites
- Local repository checkout
- Shell access
- Recent git history (for tailored suggestions)
Versioning
- info:Release ManagementNo explicit versioning is declared in the frontmatter or manifest, and installation instructions may point to `main`.
Installation
/plugin install swe-skills@ckorhonen-swe-skillsQuality Score
VerifiedTrust Signals
Similar Extensions
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
Migrate Validate
100Validate pending migrations for foreign key consistency, rollback safety, and best practices
Semgrep Rule Creator
100Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Use when writing Semgrep rules or building custom static analysis detections.
Cleanup Cycles
100Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Wrap Up Ritual
100End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.