Rechercher

PythonReactSEOPDF
GitHub Skill

shared-release-workflow

Enforces the two-stage shared→backend workflow (publish shared first, then consume from registry). Use when changing both shared/ and backend/ or when shared package versioning/publishing is involved.

piquet-h☆ 0 Étoiles du dépôt0 Forks du dépôt

Installation

Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.

Voir la source ↗Guides

Instructions

Shared release workflow

Use this skill when you are asked to:

  • Add new exports to shared/ and use them in backend/.
  • Bump @piquet-h/shared and ensure backend installs from the registry.
  • Prevent “combined PR touches shared + backend and breaks CI” situations.

Rules

  1. Never change backend to depend on file:../shared.
  2. If behavior requires new shared exports, split into two PRs:
    • PR 1: shared/ only (bump version, publish)
    • PR 2: backend integrates the published version

Helper script

  • scripts/detect-cross-package.mjs — detects when the current diff touches both shared/ and backend/.

Use this script as an early warning. It is not a replacement for code review.


Last reviewed: 2026-01-15

Exemples

Consultez les exemples du dépôt source.

Voir la source ↗

Historique source

Date d’indexation
2026-01-20
Mise à jour de l’index
2026-01-26
Branch
main

Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!