axelix

Review configuration property changes in the Axelix project for breaking changes and migration-policy compliance. Use this skill whenever a diff, PR, or commit touches Spring Boot configuration properties (@ConfigurationProperties classes, application.yml/.properties, spring-configuration-metadata) OR Helm chart values (values.yaml, values.schema.json, templates) — including any rename, removal, type/format change, or default-value change of a property or value. Trigger it even when the user only says "review this PR", "check for breaking changes", "review the config/values changes", or when a diff adds, removes, or renames keys in values.yaml or a configuration-properties class. It catches in-place renames, removal of non-deprecated properties, type/format changes, and default-value changes, and applies the "breaking-change" label when a breaking change is present.

Reviews changes in sbs/starter-domain for technology-agnostic domain logic, forbidden production dependencies, and Java 11+ compatibility. Use whenever a PR or diff touches sbs/starter-domain/, when the user asks to review starter-domain code, when evaluating starter-domain build.gradle.kts dependency changes, or when reviewing shared starter logic that must work across axelix-spring-boot-2/3/4 starters — even if the user only says "review this PR" and starter-domain files are in the diff.

Reviews test code in GitHub pull requests for isolation, public-API contract coverage, AAA structure, and correct exception assertions. Use whenever reviewing a PR that adds, modifies, or deletes tests (Java, Kotlin, TypeScript, JavaScript), when the user asks to review tests or test quality, when evaluating whether test changes are merge-ready, or when commenting on PR test coverage — even if the user only says "review this PR" and the diff includes test files.

Create batched Dependabot-style pull requests for GitHub security findings in `axelixlabs/axelix`, grouped by dependency surface such as `master/front-end`, `master/build.gradle.kts`, or starter Gradle builds. Use this skill whenever the user asks to fix CodeQL, Trivy, SARIF, Dependabot, SAST, SCA, CVE, GHSA, or `security-check` findings for the Axelix repository and wants patch-release-safe PRs that bundle related vulnerabilities by manifest or module area instead of one PR per CVE.

Refine and triage GitHub backlog by finding open issues that are stale, obsolete, or resolved by another path. Use this skill whenever the user asks about stale issues, backlog hygiene, issue triage, closing old tickets, reviewing open GitHub issues, whether an issue still applies, or reconciling issue text with the actual codebase—including when the ticket’s proposed fix was abandoned in favor of a different solution. Use it for axelixlabs repositories or whenever the goal is to cross-check GitHub issues against the current repo state (not just by last-updated dates). Triggers often include “refine backlog,” “which issues can we close,” “is this issue still valid,” or “audit open issues.”

Generates user-facing English documentation in `docs/docs/` for a single feature, module, or component implemented in `master/` (the Axelix backend) or `sbs/` (the Spring Boot Starter modules). For UI-surfaced features the skill also reads `front-end/` as the source of truth for what the user actually sees. Use this skill whenever the user asks to document, write docs for, describe, or explain — for the Axelix docs site — any backend feature (an endpoint, an autoconfiguration, a service, a discovery prober, an authentication mechanism), any starter behavior (Axelix Spring Boot 2 / 3 starter, an auto-configuration, a metrics/transaction/scheduled-task integration), or any UI page surfaced in the Axelix UI. Trigger phrases include "document the X feature", "write docs for X", "add a docs page for X", "describe how X works in docs/", "we need a Docusaurus page about X". Prefer this skill over generic Markdown writing whenever the target lives in `master/`, `sbs/`, or `front-end/` and the output goes into `docs/`

Pick open GitHub issues in the Axelix monorepo that are suitable for unpaid volunteer contributors working in their spare time. Use this skill when the user asks for “good issues for external contributors,” “interesting tickets for newcomers,” “what can volunteers pick up,” “community-friendly issues,” or wants a shortlist ranked by fit for someone with limited product context who will not commit to deadlines. Also use when comparing issues for “nice to have” vs release-critical work, or when the goal is to avoid chores/refactors/backports for volunteers. Default repo is axelixlabs/axelix (resolve from git origin when in this workspace).

Perform housekeeping tasks to manage the complexity of the code base. Use this skill when asked to perform tasks related to maintenance of the repository, refactoring of any kind, management of the technical debt or writing/revisiting tests.