Files
meshcore-analyzer/docs/agents/skills
Alex B 893773338e chore(tests): move root test-*.js into tests/unit and tests/e2e (#2036)
Moves 290 root test-*.js into tests/unit (177, listed in test-all.sh) and tests/e2e (113, classified in scripts/non-unit-tests.json), per #1981 and PR-D of #1385. Root goes from 348 entries to 48. test-all.sh and test-fixtures/ stay put. The inventory guard now fails if a test reappears in the root or sits in the wrong folder.

Verified independently of the diff: the invoked sets are unchanged (test-all.sh 177 before and after, deploy.yml 96 before and after, both identical as sets), and a full local run of test-all.sh on master and on the branch produced 4702 output lines each whose only differences are absolute paths, stack-trace line numbers shifted by the REPO_ROOT line, the inventory wording and two perf ratios. The guard was mutation-checked: a test back in the root, a unit suite in tests/e2e, and a suite dropped from test-all.sh each make it exit 1. CI run 35246304316 ran 97 suites from tests/e2e and is green.

Follow-up 9335c51d finished the instruction files: no bare root test command is left in AGENTS.md, the squad charters, .github or docs, and every tests/ path they name resolves.

Merged by the interim maintainer without a second human reviewer: CI and the local runs above are the independent checks.

Known and deliberately out of scope: 18 of the 113 files in tests/e2e are invoked by no runner at all, and one of them cannot run anywhere because it requires jsdom, which is not a declared dependency. Tracked separately.
2026-09-17 19:06:07 +02:00
..

Skills

Skills are task-specific playbooks an agent can load when it gets a particular kind of request. Each file here is self-contained — name, description/triggers, inputs, steps, output format, and failure modes.

These are written in a structure we use internally, but the shape is portable: you can paste any of these into a Claude Code / Codex / Cursor / Aider / OpenClaw system prompt or rule file and the agent will follow it.

Index

Intake & triage

  • bug-intake — diagnose a bug with expert personas; identify root causes, severity.
  • feature-intake — refine a vague feature request into a locked, implementable spec.
  • triage-sweep — bulk-categorize open issues across multiple lanes.

Implementation

  • fix-issue — end-to-end issue fix: implement, open PR, watch CI, auto-fix, hand off to polish.
  • debug-repro — reproduce bugs locally against fixture/staging before fixing.

PR pipeline

  • ci-watcher — lightweight watcher that polls CI checks and notifies on flip.
  • pr-preflight — pre-submission gate of fast fail-fast greps (run BEFORE gh pr create).
  • pr-polish — adversarial + expert + Kent-Beck review fan-out in parallel.
  • pr-merge-gate — three-axis pre-merge check (mergeable + CI + reviews).

Release & ops

  • corescope-release — release tag + deploy + verification flow.
  • devops-fix — live operational fixes on staging/prod (SSH, docker, sqlite, log triage).
  • qa-suite — full QA sweep against a running instance.

Language-specific quality gates

Meta

Adapting these to your agent

  • The skills assume a read/edit/exec style tool surface and a gh CLI. Substitute whatever your harness uses.
  • Trigger phrases are suggestions; map them to your harness's slash-command or rule-matching system.
  • Paths inside the skills use placeholders like <workspace>, <repo>, <home> — replace with your actual layout.