Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wasabeef/상황-분석-후-최적-역할접근법-자동-제안
상황 분석 후 최적 역할·접근법 자동 제안. 「리뷰해줘」「코드 품질 체크」「최적 접근법은?」등으로 기동.
Passed 25 of 25 test cases with the skill, and 14 of 25 without it.
and 11 more in the full report
11 fixed14 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running analysis on an entire project containing React, TypeScript, Auth, API, and Mobile modules, what sequence of 4 recommended steps should be suggested?
| Checked | Without skill | With skill |
|---|---|---|
| Lists security as step 1 in the workflow sequence | Missed | Passed |
| Lists architect as step 4 in the workflow sequence | Missed | Passed |
The instructions your model reads when the skill loads.
현재 상황을 분석하여 최적인 역할·접근법을 자동 제안하는 명령어입니다.
/smart-review # 현재 디렉터리를 분석
/smart-review <파일/디렉터리> # 특정 대상을 분석
package.json, *.tsx, *.jsx, *.css, *.scss → frontendDockerfile, docker-compose.yml, *.yaml → architect*.test.js, *.spec.ts, test/, __tests__/ → qa*.rs, Cargo.toml, performance/ → performanceauth.js, security.yml, .env, config/auth/ → securitylogin.tsx, signup.js, jwt.js → security + frontendapi/auth/, middleware/auth/ → security + architectmobile/ + *.swift, *.kt, react-native/ → mobilewebpack.config.js, vite.config.js, large-dataset/ → performancecomponents/ + responsive.css → frontend + mobileapi/ + auth/ → security + architecterror.log, crash.log → analyzermemory leak, high CPU, slow query → performance + analyzerSQL injection, XSS, CSRF → security + analyzertest cases passed, vs 14 / 25 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.