mateuszkruk1303/raven-workflow

raven-merge

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

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-merge

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 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.

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-pr

Push the branch and create or update the PR of the given change, linked to its issue or external ticket. Only on explicit request; no merge.

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.