OPF

Reformuler, utiliser screenshots/logs, gérer les fuseaux. Use this skill whenever the user asks about empathie asynchrone in an open-source maintenance context — including phrasing like "répondre à un contributeur", "gérer une conversation asynchrone", "communiquer avec la communauté" — even if they don't name the skill directly.

Refuser une PR en proposant systématiquement une solution. Use this skill whenever the user asks about feedback constructif in an open-source maintenance context — including phrasing like "refuser cette pr", "décliner une contribution", "donner un feedback difficile" — even if they don't name the skill directly.

Répondre, reproduire et orienter vers les 'good first issue'. Use this skill whenever the user asks about triage issues in an open-source maintenance context — including phrasing like "trier les issues", "qualifier ce bug report", "good first issue" — even if they don't name the skill directly.

Traquer les régressions avec bisect. Use this skill whenever the user asks about bug track in an open-source maintenance context — including phrasing like "trouver quel commit a cassé", "bisect", "traquer une régression" — even if they don't name the skill directly.

Gérer les erreurs prod et les réversions. Use this skill whenever the user asks about cherry pick in an open-source maintenance context — including phrasing like "revert ce commit", "cherry-pick un hotfix", "porter un fix sur une autre branche" — even if they don't name the skill directly.

Naviguer dans les submodules et monorepos. Use this skill whenever the user asks about projecte master in an open-source maintenance context — including phrasing like "gérer mes submodules", "structurer un monorepo", "migrer vers un monorepo" — even if they don't name the skill directly.

Nettoyer l'historique avec -i avant PR. Use this skill whenever the user asks about rebase in an open-source maintenance context — including phrasing like "nettoyer mon historique", "squash mes commits", "rebase interactif", "rebase avant pr" — even if they don't name the skill directly.

Écrire des workflows YAML multi-OS. Use this skill whenever the user asks about actions ci in an open-source maintenance context — including phrasing like "configurer la ci", "écrire un workflow github actions", "pipeline multi-os" — even if they don't name the skill directly.

Utiliser la CLI GitHub et Copilot en terminal. Use this skill whenever the user asks about gh cli in an open-source maintenance context — including phrasing like "utiliser gh cli", "scripter des actions github depuis le terminal" — even if they don't name the skill directly.

Maîtriser templates, labels, milestones et Projects v2. Use this skill whenever the user asks about issues projects in an open-source maintenance context — including phrasing like "créer un template d'issue", "organiser mes labels", "configurer projects v2" — even if they don't name the skill directly.

Mettre en place CLA ou DCO selon le contexte du projet. Use this skill whenever the user asks about contributor agreements in an open-source maintenance context — including phrasing like "cla ou dco", "faire signer un accord de contribution", "gérer le copyright des contributions" — even if they don't name the skill directly.

Choisir et faire respecter une licence adaptée au projet. Use this skill whenever the user asks about license choice in an open-source maintenance context — including phrasing like "choisir une licence", "mit ou apache", "changer de licence" — even if they don't name the skill directly.

Rédiger des commits selon Conventional Commits. Use this skill whenever the user asks about atomic commits in an open-source maintenance context — including phrasing like "rédiger un message de commit", "conventional commits", "structurer mes commits" — even if they don't name the skill directly.

Faire des reviews séparant fond/forme avec empathie. Use this skill whenever the user asks about review bienveillante in an open-source maintenance context — including phrasing like "review cette pr", "code review", "relire cette pull request" — even if they don't name the skill directly.

Se relire en mode diff avant de demander une review. Use this skill whenever the user asks about self review in an open-source maintenance context — including phrasing like "me relire avant de demander une review", "self review", "vérifier mon diff avant pr" — even if they don't name the skill directly.

Détecter et réduire le risque structurel d'un projet critique porté par une seule personne. Use this skill whenever the user asks about lone maintainer risk in an open-source maintenance context — including phrasing like "risque mainteneur unique", "prévenir une attaque type xz", "bus factor du projet" — even if they don't name the skill directly.

Produire un SBOM et signer les artefacts de release. Use this skill whenever the user asks about sbom provenance in an open-source maintenance context — including phrasing like "générer un sbom", "signer une release", "prouver la provenance du build" — even if they don't name the skill directly.

Utiliser OpenSSF Scorecard comme check-list de sécurité objective. Use this skill whenever the user asks about scorecard baseline in an open-source maintenance context — including phrasing like "évaluer la sécurité du projet", "openssf scorecard", "auditer mes dépendances" — even if they don't name the skill directly.

Distinguer une contribution IA légitime d'un volume à faible valeur généré sans supervision. Use this skill whenever the user asks about ai slop detection in an open-source maintenance context — including phrasing like "détecter une pr générée par ia", "trier des contributions à faible valeur", "reconnaître du slop" — even if they don't name the skill directly.

Adapter les métriques de santé de projet à un contexte où produire un événement (issue/commit) ne coûte plus rien. Use this skill whenever the user asks about metrics recalibration in an open-source maintenance context — including phrasing like "recalibrer nos métriques de santé", "mesurer la santé du projet en 2026", "métriques chaoss" — even if they don't name the skill directly.

Reconnaître et prévenir l'épuisement du ou des mainteneurs. Use this skill whenever the user asks about burnout prevention in an open-source maintenance context — including phrasing like "éviter le burnout", "je suis débordé par les issues", "prévenir l'épuisement du mainteneur" — even if they don't name the skill directly.

Mettre en place un canal de financement adapté à la taille du projet. Use this skill whenever the user asks about funding setup in an open-source maintenance context — including phrasing like "financer le projet", "mettre en place github sponsors", "chercher un financement open source" — even if they don't name the skill directly.

Utiliser Typedoc/Sphinx et maintenir README/CONTRIBUTING. Use this skill whenever the user asks about doc as code in an open-source maintenance context — including phrasing like "générer la documentation", "mettre à jour le readme", "maintenir la doc à jour" — even if they don't name the skill directly.

Gérer les secrets et les dépendances avec Dependabot. Use this skill whenever the user asks about security dependabot in an open-source maintenance context — including phrasing like "auditer les dépendances", "configurer dependabot", "scanner les secrets" — even if they don't name the skill directly.

Écrire des tests en TDD (unitaires + intégration). Use this skill whenever the user asks about tdd tests in an open-source maintenance context — including phrasing like "écrire des tests", "faire du tdd", "tester cette fonctionnalité" — even if they don't name the skill directly.