القائمة
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when writing tests, running tests, adding test coverage, or debugging test failures. Detects the language and its test runner (JS/TS, Python, Go, Rust) for unit and component testing.
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits in the repository's own convention (conventional commits, area prefix, tracker ID, or plain) with secret scanning (GitLeaks).
Use when creating a branch, starting work on an issue, or checking out a new feature branch. Validates branch naming and links to GitHub issues automatically.
Use when opening a PR, submitting for review, pushing a branch, or creating a pull request. Pushes and creates GitHub PRs with auto-assignment and description.
Use when hardening a dependency supply chain, pinning versions, adding registry/security flags, or setting up Renovate. Detects the language and locks down install scripts, versions, and CI checks (JS/TS, Python, Go, Rust).
Use when adding CI/CD, creating workflows, auditing GitHub Actions, or fixing action pinning. Creates and audits workflows for SHA pinning and permissions.
استنادا إلى تصنيف SOC المهني
| name | refactor |
| description | Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns. |
| license | MIT |
| allowed-tools | Read Glob Grep Edit |
| model | sonnet |
| effort | high |
| context | fork |
| agent | general-purpose |
| compatibility | Any language; general + design rules always apply, the TS/JS idiom rules apply only to TS/JS files |
| metadata | {"short-description":"Refactor and reduce code complexity."} |
You are an expert code reviewer focused on refactoring.
Audit and report by default; edit files only when the user asks you to fix, refactor, apply, or clean something up. When the ask is unclear, report first and offer to apply the fixes.
| Rules | Scope | File |
|---|---|---|
| General patterns | any language | rules/general-patterns.md |
| TypeScript/JS idioms | .ts/.tsx/.js/.jsx/.mts/.cts only | rules/ts-idioms.md |
| Design principles | any language | rules/design-principles.md |
Scan the target scope (specific files, directory, or full codebase) against every rule in rules/.
Report each finding as path:line — what is wrong → the fix, grouped by category, and close with a per-category violation count.
Apply refactorings. For each fix:
