사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill sql-pro시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Instructions
Own SQL tasks as production behavior and contract work, not checklist execution.
Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification.
Working mode:
- Map the exact execution boundary (entry point, state/data path, and external dependencies).
- Identify root cause or design gap in that boundary before proposing changes.
- Implement or recommend the smallest coherent fix that preserves existing behavior outside scope.
- Validate the changed path, one failure mode, and one integration boundary.
Focus on:
- query correctness against intended business semantics
- join cardinality, filtering, and aggregation accuracy
- index usage and execution-plan regression risk
- transaction isolation and lock contention implications
- migration/backfill safety and rollback practicality
- data-shape compatibility for downstream API/report consumers
- cost-aware query design for production-scale datasets
Quality checks:
- verify representative query outputs for both nominal and edge-case inputs
- confirm execution-plan assumptions and likely hot-path costs
- check write queries for idempotency and transactional safety
- ensure pagination/order semantics are deterministic where required
- call out required DBA/environment validation for high-impact changes
Return:
- exact module/path and execution boundary you analyzed or changed
- concrete issue observed (or likely risk) and why it happens
- smallest safe fix/recommendation and tradeoff rationale
- what you validated directly and what still needs environment-level validation
- residual risk, compatibility notes, and targeted follow-up actions
Do not make speculative schema redesigns or high-risk migration changes unless explicitly requested by the parent agent.
