change-managementControl a change delivered to a shared or production environment - change record and register, risk class, approval with segregation of duties, deployment and verification, release tagging, emergency change with retroactive review. Use for "déploiement en production", "mise en prod", "registre des c
dev-traceabilityGuarantee a traceable path from requirement to merged change - requirement → issue → commit → PR → review → tests, traceability matrix (RTM), definition of done, compliance report aligned with ISO/IEC 27001:2022, ISO 9001, ISO/IEC/IEEE 12207, ITIL 4 and SOC 2. Use for any feature or fix, or to "prép
incident-responseHandle a security or operations incident - P1-P4 qualification, containment, evidence preservation, register, notification decision (drafts only), recovery, blameless post-mortem. Use for "incident", "fuite", "fraude", "panne en production", "réclamation grave". Not for an ordinary bug (use issue-li
issue-lifecycleFull lifecycle of an error in GitHub Issues - record it, keep a timestamped resolution journal, document the root cause, fix through the project's PR flow, verify, close. Use when an error takes more than one attempt to understand, touches CI, deployment, security or authentication, or may come back
project-boardBuild and run the follow-up of the repository's GitHub Project - standard fields (priority, kind, estimate, target date, iteration), 15 standard views (board, backlog, current iteration, roadmap, epics, by epic, without epic, my work, needs triage, in review, blocked, bugs, security, stale, done), f
project-trackingKeep every GitHub issue and open pull request in the repository's GitHub Project and every issue under an epic (native sub-issues) - choose or create the Project (confirmed by the user, as visible as the repository), attach, move or detach issues, show the epic hierarchy, find and repair orphans. Us
repo-contextConnect to and remember the active GitHub repository (fully gh-compatible) - resolves owner/repo, host, default branch, visibility, permission and auth state from the current directory, caches labels and learned per-repo facts. Use before any `gh` command or whenever another skill needs the project'
repo-hardeningAudit and, on explicit request, apply the protections of a GitHub repository - default-branch protection or rulesets (required review and status checks, no force-push), secret scanning and push protection, Dependabot, CODEOWNERS, PR and issue templates, Actions permissions and pinned actions, Enviro
secrets-hygieneAudit, generate, rotate and roll back a project's technical secrets and accounts (database passwords, API keys, tokens, webhook secrets) without ever reading or displaying a value. Use for "rotation des secrets", "mot de passe par défaut", "secret exposé", "ajoute un compte au registre", "rollback d
security-auditApplication security audit before a release or as a periodic review - route authentication and authorization, default secrets, exposed ports, webhook signatures, sensitive-data access, logging, input validation, dependencies, monitoring. Use for "audit sécurité", "revue d'accès", "avant la prod". Re
skill-learningLearn from how skills are actually used so they improve over time - logs the outcome of each skill run and the user's corrections to a local history, summarises success rates and recurring frictions, and drafts reviewed improvements to the skills repository. Use when the user corrects how a skill be