en un clic
fragalysis-backend
fragalysis-backend contient 5 skills collectées depuis xchem, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Build a developer Fragalysis Stack (backend + stack container images) and then deploy it to Kubernetes by triggering the developer's AWX Job Template
Work on a GitHub issue end-to-end in a git worktree — move its board card to In Progress first, read the issue, explore the code, branch from staging, write the test first (TDD), commit, and open a PR. Use when the user says e.g. "work on issue 958", "start issue 1234", "/issue N", or asks to take a fragalysis-backend issue from triage to PR.
Release the staging branch to production. Opens a staging→production PR, waits for CI, merges it (keeping staging), then publishes a YYYY.MM.ITERATION GitHub release of production. Use when the user asks to "release staging", "do a release", or "release the staging branch".
Finalise a Release ticket on the m2ms Fragalysis project board — move every "fragalysis-backend"-labelled issue from the "Approved in staging - push to production" swimlane into "In production (Done)" and list them on the Release ticket. Use after a staging→production release, when the user says e.g. "finalise release 2246", "mark release 2246 done", "move the approved backend issues to production for release 2246".
Copy a project-board issue into the fragalysis-backend repo. Use when the user asks to create a backend issue from a project-board issue, e.g. "Create an issue for project issue 1234".