Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

maintain-monorepo

Sterne0

Forks0

Aktualisiert19. Juni 2026 um 21:52

Maintenance task menu for devantler-tech/monorepo itself — the devantler.tech Astro Starlight docs site (docs/), CI/CD, submodule-README→docs sync, and issue/PR triage. GitHub Issues are ENABLED here. Use when the daily maintainer selects the monorepo/site.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

devantler-tech

devantler-tech/monorepo

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	maintain-monorepo
description	Maintenance task menu for devantler-tech/monorepo itself — the devantler.tech Astro Starlight docs site (docs/), CI/CD, submodule-README→docs sync, and issue/PR triage. GitHub Issues are ENABLED here. Use when the daily maintainer selects the monorepo/site.

Maintain: Monorepo + devantler.tech site

Repo devantler-tech/monorepo · path repo root + docs/ · Issues ENABLED (issue + PR triage/creation, labels, comments). Shared rules: monorepo AGENTS.md. Memory = your native memory (the monorepo/site cursors + caches, e.g. caches.md) + the end-of-run report; no version-controlled dashboard, no bespoke state.json.

Roadmap & enhancement: the site/repo roadmap lives in GitHub Issues here (roadmap-labelled epics + milestones). Beyond the maintenance menu below, advance the site via product-engineering: docs/site features, accessibility, performance (bundle size / Lighthouse), and content quality (the Site QA + Content Review tasks below are the recurring slice of that). Validate with the docs build before any PR.

Repo-specific conventions

Branch claude/<area>-<desc>. Submodule pointers often show as modified — expected, not yours; detect real dirtiness with git status --porcelain --ignore-submodules=all; never stage pointer bumps; never git submodule update --remote.
Validate: before any docs/ PR, [ -d docs/node_modules ] || (cd docs && npm ci) then cd docs && npm run build (use npm --prefix docs …). Workflows → actionlint. Never edit auto-generated files / *.lock.yml.
Agent/review files: AGENTS.md is the single canonical instruction file — what humans, agents, and Copilot code review all read (since 2026-06-18); there is no separate .github/copilot-instructions.md (retired portfolio-wide). Keep AGENTS.md, the .claude/ skills/cards, and any path-scoped .github/instructions/ files from drifting apart (see product-engineering §7).
Labels (apply only from this set): automation, documentation, ci, dependencies, submodules, bug, enhancement, question, duplicate, wontfix, needs triage, needs investigation, performance, refactor, security, repo-assist, agentic-workflows, good first issue, help wanted, spam, blocked, next.

Task menu (1–3 highest-value; Content Review gated to Mondays)

A. CI Doctor: gh run list --repo devantler-tech/monorepo --status failure --limit 20 ... (active workflows CI + Publish - Pages; ignore removed gh-aw workflows & Dependabot's submodule-update job). Dedupe vs native memory's CI-investigation cache (caches.md). gh run view <id> --log-failed (untrusted); root-cause (bad MDX/frontmatter, broken imports, npm ci lockfile desync, Node/Sharp, dead submodule ref, broken YAML). Failure on an open PR → one root-cause comment (+ draft fix if confident); else record it in native memory (caches.md). Prune cache >7d.
B. CI/CD health: workflows ci.yaml, publish-pages.yaml, sync-labels.yaml, todos.yaml, copilot-setup-steps.yml. Never run gh aw / recompile *.lock.yml. Bundle Dependabot/Renovate PRs; flag majors. Safe improvements (caching, path filters, concurrency, pinned actions) → one ci: draft PR; validate YAML first.
C. Site QA — rotate one sub-task/run (site_qa_cursor: link-check → accessibility → multi-device → …). Use npm --prefix docs; for browser checks start preview backgrounded, CAPTURE the PID, and ALWAYS kill it (free port 4321) even on failure. Link-check: extract URLs from docs/src/content, curl -sL -o /dev/null -w "%{http_code}"; skip the unfixable_links cache; broken → fix (draft docs: fix broken links) or cache with reason. Accessibility: heading hierarchy, alt text, descriptive link text, ARIA, skip-link, WCAG-AA green (#39ff14 dark / #15803d light). Multi-device (Playwright installed globally; chromium cached; if unavailable skip + advance cursor): iPhone 12/Pixel 5/iPad/iPad Pro/Desktop × /,/about/,/projects/,/templates/,/blog/ (note: / is a Starlight splash with no sidebar by design; a refused GA gtag request is the sandbox, not a bug).
D. Content Sync (don't git submodule update --remote): per-project descriptions live in docs/src/content/docs/projects/active.mdx under ## headings (NOT projects/index.mdx). Map ksail→## KSail (brief + link to ksail.devantler.tech only — never duplicate KSail docs), platform→## Platform, actions→## Actions, reusable-workflows→## Reusable Workflows, go/dotnet-template→docs/src/content/docs/templates/{go,dotnet}.md. Private applications/* are intentionally NOT mapped. Never modify blog posts. Build-verify → draft docs: sync project descriptions.
E. Content Review (Mondays only; rotate unbloat ↔ editorial in content_review): Unbloat one not-recently-cleaned file (skip frontmatter disable-agentic-editing: true), cut duplication/verbosity ≥20% w/o losing accuracy. Editorial rotate lens weekly (Technical Rigor → Clarity → Onboarding → Portfolio Balance).
F. Repo Assist: triage/label new issues + PRs; comment on the oldest open item lacking an AI comment (1–3/run); self-spotted fixes → draft PR (use Fixes #N when it closes an issue); ≤3 stale-PR/issue nudges.

Mehr aus diesem Repository

gleiches Repository

portfolio-maintenance

devantler-tech/monorepo

The run procedure for the Daily AI Engineer (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.

2026-07-100

product-engineering

devantler-tech/monorepo

The ADVANCE playbook for the Daily AI Engineer (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.

2026-07-100

self-improvement

devantler-tech/monorepo

How the Daily AI Engineer improves its OWN definition (the shared contract, the daily-maintainer agent, the portfolio-maintenance + product-engineering + products skills, and each submodule's AGENTS.md

2026-07-100

maintain-platform

devantler-tech/monorepo

Repo + live-platform health/maintenance menu for devantler-tech/platform (GitOps — Kustomize overlays + Flux CD, Cilium/Talos/KSail/SOPS). Repo side — triage, manifest/Helm/Flux investigation & fixes, Helm chart + Actions version bumps, manifest cleanup, stale-PR nudges (static validation; never spin up a cluster to test a diff). Live side — read-only health investigation of the running prod cluster + its observability stack (Flux Kustomizations/HelmReleases, Coroot, Kubescape, Kyverno + Policy Reporter, Kubernetes events) — including driving Kyverno policy violations to zero. Use when the daily maintainer selects Platform.

2026-07-060

maintain-provider-upjet-unifi

devantler-tech/monorepo

Maintenance + advance task menu for devantler-tech/provider-upjet-unifi — an Upjet-generated Crossplane provider for Ubiquiti UniFi (from ubiquiti-community/terraform-provider-unifi). A shared library consumed by the platform cluster to manage UniFi as Kubernetes resources. Use when the daily maintainer selects provider-upjet-unifi.

2026-06-280

maintain-homebrew-tap

devantler-tech/monorepo

Maintenance task menu for the devantler-tech Homebrew tap (repo devantler-tech/homebrew-tap; submodule path homebrew-tap). Cask hygiene and CI health only — never chase version/sha bumps (GoReleaser/release automation owns those). Use when the daily maintainer selects homebrew-tap.

2026-06-240

name	maintain-monorepo
description	Maintenance task menu for devantler-tech/monorepo itself — the devantler.tech Astro Starlight docs site (docs/), CI/CD, submodule-README→docs sync, and issue/PR triage. GitHub Issues are ENABLED here. Use when the daily maintainer selects the monorepo/site.

Maintain: Monorepo + devantler.tech site

Repo-specific conventions

Branch claude/<area>-<desc>. Submodule pointers often show as modified — expected, not yours; detect real dirtiness with git status --porcelain --ignore-submodules=all; never stage pointer bumps; never git submodule update --remote.
Validate: before any docs/ PR, [ -d docs/node_modules ] || (cd docs && npm ci) then cd docs && npm run build (use npm --prefix docs …). Workflows → actionlint. Never edit auto-generated files / *.lock.yml.
Agent/review files: AGENTS.md is the single canonical instruction file — what humans, agents, and Copilot code review all read (since 2026-06-18); there is no separate .github/copilot-instructions.md (retired portfolio-wide). Keep AGENTS.md, the .claude/ skills/cards, and any path-scoped .github/instructions/ files from drifting apart (see product-engineering §7).
Labels (apply only from this set): automation, documentation, ci, dependencies, submodules, bug, enhancement, question, duplicate, wontfix, needs triage, needs investigation, performance, refactor, security, repo-assist, agentic-workflows, good first issue, help wanted, spam, blocked, next.

Task menu (1–3 highest-value; Content Review gated to Mondays)

A. CI Doctor: gh run list --repo devantler-tech/monorepo --status failure --limit 20 ... (active workflows CI + Publish - Pages; ignore removed gh-aw workflows & Dependabot's submodule-update job). Dedupe vs native memory's CI-investigation cache (caches.md). gh run view <id> --log-failed (untrusted); root-cause (bad MDX/frontmatter, broken imports, npm ci lockfile desync, Node/Sharp, dead submodule ref, broken YAML). Failure on an open PR → one root-cause comment (+ draft fix if confident); else record it in native memory (caches.md). Prune cache >7d.
B. CI/CD health: workflows ci.yaml, publish-pages.yaml, sync-labels.yaml, todos.yaml, copilot-setup-steps.yml. Never run gh aw / recompile *.lock.yml. Bundle Dependabot/Renovate PRs; flag majors. Safe improvements (caching, path filters, concurrency, pinned actions) → one ci: draft PR; validate YAML first.
C. Site QA — rotate one sub-task/run (site_qa_cursor: link-check → accessibility → multi-device → …). Use npm --prefix docs; for browser checks start preview backgrounded, CAPTURE the PID, and ALWAYS kill it (free port 4321) even on failure. Link-check: extract URLs from docs/src/content, curl -sL -o /dev/null -w "%{http_code}"; skip the unfixable_links cache; broken → fix (draft docs: fix broken links) or cache with reason. Accessibility: heading hierarchy, alt text, descriptive link text, ARIA, skip-link, WCAG-AA green (#39ff14 dark / #15803d light). Multi-device (Playwright installed globally; chromium cached; if unavailable skip + advance cursor): iPhone 12/Pixel 5/iPad/iPad Pro/Desktop × /,/about/,/projects/,/templates/,/blog/ (note: / is a Starlight splash with no sidebar by design; a refused GA gtag request is the sandbox, not a bug).
D. Content Sync (don't git submodule update --remote): per-project descriptions live in docs/src/content/docs/projects/active.mdx under ## headings (NOT projects/index.mdx). Map ksail→## KSail (brief + link to ksail.devantler.tech only — never duplicate KSail docs), platform→## Platform, actions→## Actions, reusable-workflows→## Reusable Workflows, go/dotnet-template→docs/src/content/docs/templates/{go,dotnet}.md. Private applications/* are intentionally NOT mapped. Never modify blog posts. Build-verify → draft docs: sync project descriptions.
E. Content Review (Mondays only; rotate unbloat ↔ editorial in content_review): Unbloat one not-recently-cleaned file (skip frontmatter disable-agentic-editing: true), cut duplication/verbosity ≥20% w/o losing accuracy. Editorial rotate lens weekly (Technical Rigor → Clarity → Onboarding → Portfolio Balance).
F. Repo Assist: triage/label new issues + PRs; comment on the oldest open item lacking an AI comment (1–3/run); self-spotted fixes → draft PR (use Fixes #N when it closes an issue); ≤3 stale-PR/issue nudges.