사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-pr-comments시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Make every agent-written comment easy to spot, short and safe to publish.
Steps
- Write the reply. Lead with the conclusion. Cite the code line, check, test or reproduction that supports it. Mark what you verified and what is your opinion.
- Put this note at the top, with the reply below it:
md
> [!NOTE]
> **<model> responding on behalf of <user>**
Reply text starts here.Use the model name the harness reports. If it reports none, use the harness name. Use the user's name or GitHub login.
- Scan the full comment, including quotes and attachments, for secrets, tokens, private paths and personal data. Remove them.
- Preview the final Markdown. Confirm the note and the reply render as two separate blocks.
- Post the comment.
- Confirm GitHub returned the comment or review URL. Print it.
- Resolve a review thread only after its reply posted.
Stop when
- GitHub returned a URL for each comment you meant to post.
- A post fails twice. Report the error and do not resolve the thread.
Rules
- Use the note on top-level comments, inline review comments, replies to bots and people, and dismissal reasons.
- Do not use it in PR descriptions, commit messages or text the user asked to post word for word.
- One attribution only. No signature, footer, heading or horizontal rule.
- No thanks, filler or status updates such as "still working on it".
- Never guess the model name.
