mateuszkruk1303/raven-workflow

raven-pr

Push the branch and create or update the PR of the given change, linked to its issue or external ticket.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mateuszkruk1303/raven-workflow --skill raven-pr

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Raven PR

Follow working on GitHub tasks. Talk to the user in their language; write the PR description in the language the repository uses.

Invoking raven-pr is consent to an ordinary push of the current branch and to creating or updating its PR. Do not ask for it again.

  1. Determine the repo, branch, base and issue or external ticket (from the argument, the context or the key in the branch name). When the current branch is the default branch, create a new branch from HEAD following the project's convention (git switch -c) and push only that; do not reset the local default branch, and say in chat that it is ahead of the remote. Never push directly to the default branch. Check the working tree: only your own work goes into a commit, other people's changes stay untouched. Commit your own uncommitted work in logical steps.
  2. Find an existing PR for this branch; update it instead of creating a duplicate. After a timeout, read the state first, then retry if needed.
  3. Ordinary push, no force-push. PR description: problem and outcome, Closes #N, or for ticket work the ticket per external ticket (an explicit issue wins), scope, a ## Verification section per the rules, known gaps. Take the verification from the final message of raven-auto-implement, raven-test or a review in the current context; do not add checks you cannot see. When updating the PR, refresh the section with new checks. Pass a multi-line body through a file (--body-file). Draft when the user asks for it or the work is incomplete.
  4. Read the PR back after writing (URL, head, base, state) and give it in chat together with any gaps.

Do not merge, change branch protection or close the issue. A local test result is not CI.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
mateuszkruk1303
커뮤니티

raven-auto-implement

Carry out the user's instruction, optionally with a given GitHub issue, plan or external ticket link (Jira, Linear and similar) read as the specification, verify the change at a quick, standard or thorough level matched to risk, and summarize the result only in the final chat message.

1시간 설치 수
1
GitHub Stars
0
업데이트
10월 20일
mateuszkruk1303
커뮤니티

raven-md

Create, update or review AGENTS.md and CLAUDE.md (or another AI instructions file) from the project's real files, commands and conventions. AGENTS.md holds the shared content, CLAUDE.md imports it. Review gives a scorecard without rewriting rules. Does not initialize context folders or the stack.

1시간 설치 수
1
GitHub Stars
0
업데이트
10월 20일
mateuszkruk1303
커뮤니티

raven-merge

Merge the given PR after green CI and the user's consent, then confirm its GitHub issue, if any, is closed. Deploy is separate.

1시간 설치 수
1
GitHub Stars
0
업데이트
10월 20일
mateuszkruk1303
커뮤니티

raven-shape

Refine an idea for a new product or a significant change to an existing system in a structured conversation about the problem, users and product scope. Write and resume shape-notes.md for Raven skills before the PRD. Use for shaping the vision, MVP scope, requirements and business rules; not for implementing a single bug.

1시간 설치 수
1
GitHub Stars
0
업데이트
10월 20일