maintain-monorepo

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

Jump to install

Repository: devantler-tech/monorepo
Last source activity: August 21, 2026 at 21:40
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/devantler-tech/monorepo --skill maintain-monorepo

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

portfolio-maintenance

The run procedure for the Agentic 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 every actionable PR to a terminal state whoever authored it, including dependency-bot PRs that cannot finish autonomously), and report. Use when maintaining or advancing the monorepo's products on a schedule or on request.

2026-08-24

product-engineering

The ADVANCE playbook for the Agentic 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, refactoring & code quality, and security hardening that never taxes developer experience. Use after the operate ladder is satisfied and you're picking proactive enhancement work.

2026-08-21

maintain-skills

Maintenance + advance task menu for the shared AGENT-EXTENSION libraries — devantler-tech/agent-skills (generic, cross-tool agent skills) and devantler-tech/agent-plugins (a tool-neutral marketplace bundling those skills for VS Code / Copilot CLI / Claude Code). Generic, cross-tool, industry-standard building blocks reused across the suite; high-care and backward-compatible. Use when the Agentic Engineer selects skills/plugins or runs the holistic shared-library review.

2026-08-21

View all from this repository

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). The blog is a maintained public product: use privacy-safe evidence to improve discovery, comprehension, adoption, and portfolio positioning through both new posts and material refreshes. Validate with the docs build before any PR.

Repo-specific conventions

Branch claude/<area>-<desc>-<issue> (the issue number makes a pre-PR claim matchable — see the contract's Claim protocol; issue-less hotfixes and trivial obvious fixes keep plain claude/<area>-<desc>). When grepping open PR bodies for #<issue>, keep only same-repo references (drop a hit whose only #<issue> is a foreign owner/repo#<issue> — a body naming both repos is still a valid local claim). 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, github_actions, dependencies, submodules, bug, enhancement, question, duplicate, wontfix, needs triage, needs investigation, performance, refactor, security, repo-assist, roadmap, good first issue, help wanted, spam, blocked, next. Live taxonomy is the verification source (gh label list -R devantler-tech/monorepo); the allowlist above must stay a subset of it — never invent label names. Contract self-test: .claude/scripts/product-value-contract.test.sh parses every backticked allowlist label against a pinned live-taxonomy set (and still rejects the retired ci / agentic-workflows entries).

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

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. Let exact Renovate/Dependabot PRs self-progress only while the root contract's live evidence qualifies; when one cannot finish autonomously, diagnose, repair, and merge it as trusted rung-one work (majors included). Safe improvements to dependency automation or workflows (caching, path filters, concurrency, pinned actions) → one issue-driven 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).