// Maintenance task menu for the shared CI/CD building blocks — devantler-tech/actions (composite actions) and devantler-tech/reusable-workflows. Load-bearing for every other repo's CI, so changes are high-care and backward-compatible. Use when the daily maintainer selects github-actions.
The run procedure for the Daily AI Assistant (the products' primary engineer) — pre-flight, survey the whole devantler-tech portfolio, select the highest-value work (operate first, then advance), act via per-run worktrees and draft PRs (driving trusted-author PRs to merge), and report. Use when maintaining or advancing the monorepo's products on a schedule or on request.
The ADVANCE playbook for the Daily AI Assistant (the products' primary engineer) — how to move a devantler-tech product forward once it's healthy: product strategy & roadmaps, issue triage & decomposition, planning & implementing issues, test coverage, benchmarking & performance, and refactoring & code quality. Use after the operate ladder is satisfied and you're picking proactive enhancement work.
How the Daily AI Assistant improves its OWN definition (the shared contract, the daily-maintainer agent, the portfolio-maintenance + product-engineering + products skills, and each submodule's AGENTS.md
Maintenance task menu for the PRIVATE platform-tenant apps — wedding-app and ascoachingogvaner (both SvelteKit + TS). Conservative: triage, dependency/security hygiene, CI health, small confident fixes. Use when the daily maintainer selects applications.
Maintenance task menu for the devantler-tech Homebrew tap (repo devantler-tech/homebrew-tap; submodule path homebrew-formulas). Cask hygiene and CI health only — never chase version/sha bumps (GoReleaser/release automation owns those). Use when the daily maintainer selects homebrew-formulas.
Maintenance task menu for devantler-tech/ksail (a Go CLI for local Kubernetes GitOps). Triage, bug fixes, CI/workflow health + CI-failure & flaky-test investigation, docs, driving trusted-author PRs to merge, weekly E2E coverage + live reliability testing, and the monthly KSail Strategy roadmap. Use when the daily maintainer selects KSail.
| name | maintain-github-actions |
| description | Maintenance task menu for the shared CI/CD building blocks — devantler-tech/actions (composite actions) and devantler-tech/reusable-workflows. Load-bearing for every other repo's CI, so changes are high-care and backward-compatible. Use when the daily maintainer selects github-actions. |
Each repo's canonical maintenance task menu lives in its own repo — read the ## Maintenance
section of each AGENTS.md (on the submodule's latest main):
github/devantler-tech/github-actions/actions/AGENTS.md — https://github.com/devantler-tech/actions/blob/main/AGENTS.mdgithub/devantler-tech/github-actions/reusable-workflows/AGENTS.md — https://github.com/devantler-tech/reusable-workflows/blob/main/AGENTS.mdBlast radius: changes here ripple to every consumer repo — prefer additive, backward-compatible
changes. Shared cross-repo rules are in the monorepo AGENTS.md. This card
is a pointer by design — each menu is maintained once, in the repo's own AGENTS.md.
Roadmaps for both repos live in GitHub Issues (roadmap label) on devantler-tech/actions and
devantler-tech/reusable-workflows. Advance via
product-engineering: new composite actions / workflow
capabilities and their tests — but because of the blast radius, keep everything additive &
backward-compatible and never break a consumer.