사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/icodecraft/anti-slop --skill pr-hygiene시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
PR Hygiene
Turn the current work into a PR a human can review in one pass.
Before opening
- [ ] Branch contains one logical change (or clearly labeled stacked commits)
- [ ] No leftover
console.log,debugger,TODO: temp, commented-out blocks you added - [ ] No unrelated formatting-only churn
- [ ] Secrets,
.env, and local-only files are not staged - [ ] Diff matches the stated goal — nothing "extra helpful"
Description template
Use this structure (adapt section names to the host: GitHub/GitLab):
markdown
## Summary
<1–3 bullets: what and why>
## Test plan
- [ ] <how you verified>
- [ ] <edge case worth checking>
## Notes
<risks, follow-ups, screenshots if UI>Commit / PR title
- Imperative, specific:
fix checkout: reject expired discount codes - Not:
update stuff,fix,WIP,address comments
Reviewer empathy
Call out:
- Files that look scary but are mechanical (renames, generated)
- Behavior that changed for callers/API consumers
- Anything you are unsure about
Anti-patterns
- NEVER mix refactor + feature + dependency bump in one PR unless required
- NEVER force-push shared branches without warning
- NEVER open a PR with "tests TBD" and no plan
- NEVER bury breaking changes in the middle of the description
If asked to open the PR
- Summarize the diff in your own words first
- Draft title + body with the template
- List residual risks in one short section
