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.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/mateuszkruk1303/raven-workflow --skill raven-pr

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
mateuszkruk1303
Communauté

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.

Installations / 1h
1
GitHub Stars
0
Mis à jour
20 oct.
mateuszkruk1303
Communauté

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.

Installations / 1h
1
GitHub Stars
0
Mis à jour
20 oct.
mateuszkruk1303
Communauté

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.

Installations / 1h
1
GitHub Stars
0
Mis à jour
20 oct.
mateuszkruk1303
Communauté

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.

Installations / 1h
1
GitHub Stars
0
Mis à jour
20 oct.