사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mateuszkruk1303/raven-workflow --skill raven-merge시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Raven Merge
Follow working on GitHub tasks. Talk to the user in their language.
The instruction "merge <PR/change>" is consent to merge the unambiguously identified PR. Do not ask for it again; with several candidates, establish which one.
Before merge
Read the current head, base, draft state, mergeability, required checks and reviews, branch protection and merge queue. FAIL, a conflict or a missing required check blocks the merge; pending means waiting. No access to protection data does not mean there is none. Do not use --admin or any bypass, and do not approve your own PR.
Merge
Use the method required by the repo policy; without a preference, the first allowed of: squash, merge commit, rebase. Merge exactly the checked head (gh pr merge --match-head-commit <SHA>); with a queue, use its mechanics. After the request, including after a timeout, read mergedAt and the merge commit; do not blindly send a second request.
After merge
Check that the linked GitHub issue is closed (ticket-only work has none; never close or transition an external ticket); if not, close it and remove the in-progress/blocked labels. If that fails, report "PR merged; issue needs closing", without reverting the merge. In chat give the PR, merge commit, issue state (if there is an issue) and the state of the local checkout. Merge does not start the next task or a deploy.
