Static Analysis

Prompt

<Scope>에 대한 모든 코드를 정적 분석하고 모든 버그를 찾아 각각 $add-issue로 등록해. 이슈를 모으지 말고 확인되는 대로 바로바로 등록해. <Scope>는 사용자가 지정하며, 생략하면 코드 전체를 대상으로 해.

Resolve the target repository from the user's request or current checkout. Treat <Scope> as the user's analysis boundary, not a literal path. If omitted, analyze all code in that repository.
Read applicable repository instructions and map the code covered by the scope. Read related contracts, configuration, tests, and callers. Read outside the scope only as needed to establish behavior and causes for in-scope defects.
A direct human invocation of $static-analysis or an explicit request to run Static Analysis authorizes this analysis run and $add-issue handoffs for bugs found within its scope. Automatic skill selection alone does not authorize issue recording.
Preserve narrower user restrictions, including draft-only reporting. Creating, editing, planning, or testing this skill does not start analysis or issue recording.
Do not fix code, commit changes in the target repository, or mutate production. Use read-only analysis tools without autofix. Leave any required candidate verification to $add-issue under its own rules.