Skip to content

mikeparcewski/wicked-garden / skills/build-guide

wicked-garden-build-guide

Verified

Discover how a repo builds and tests, and write its build/test guide (`.wicked/build-guide.json`, contract v1): the data the wicked-core floor interprets instead of hardcoding runners. Reads CI config first, then the manifests, then each runner's own --version and --help. Prefers structured results (JUnit; JSON lines and TAP are reserved in v1) and writes a text parser, learned from this repo's real output, only when none exists. Writes a deliberately failing mutation probe, validates with `wicked-core floor probe` (only the probe writes `verified`), and proposes the file as a PR or governed change, never silently. Use when: "build guide", "write the build/test guide", "how does this repo test", "onboard this repo's tests for the floor", "re-onboard the build guide", "the build guide is stale", the onboarding step of the wicked-garden-core setup action, or a wicked-crew onboarding run dispatched because the floor found no guide, a stale one, or a failed probe.

FileKindSize
SKILL.mdskill md13.7 KB
assets/seeds/cargo-libtest.jsonconfig2.6 KB
assets/seeds/pytest-short-summary.jsonconfig2.5 KB
assets/seeds/vitest-junit.jsonconfig2.0 KB
refs/contract-notes.mdmarkdown12.1 KB
refs/discover.mdmarkdown4.9 KB
refs/propose.mdmarkdown1.9 KB
refs/results.mdmarkdown7.0 KB

assets/seeds/vitest-junit.json

View on GitHub
{
  "version": 1,
  "derivedFrom": [
    ".github/workflows/ci.yml",
    "package.json"
  ],
  "checks": [
    {
      "name": "install",
      "cwd": ".",
      "run": [
        "npm",
        "install",
        "--no-audit",
        "--no-fund"
      ]
    },
    {
      "name": "test",
      "cwd": ".",
      "stage": [
        "creator",
        "verify"
      ],
      "run": [
        "npx",
        "vitest",
        "run"
      ],
      "failedExit": [
        1
      ],
      "results": {
        "kind": "junit",
        "id": [
          "name"
        ],
        "how": {
          "argvAppend": [
            "--reporter=junit",
            "--outputFile=.wicked-floor/junit.xml"
          ],
          "env": {},
          "path": ".wicked-floor/junit.xml"
        }
      },
      "list": {
        "run": [
          "npx",
          "vitest",
          "list"
        ],
        "item": "^\\S+ > (?P<id>.+)$"
      },
      "alone": {
        "run": [
          "npx",
          "vitest",
          "run",
          "--testNamePattern=^{id:re}$"
        ]
      },
      "deselect": {
        "append": [
          "--testNamePattern=^(?!(?:{ids:re|})$)"
        ]
      },
      "version": {
        "run": [
          "npx",
          "vitest",
          "--version"
        ]
      },
      "invalidatedBy": [
        "package.json",
        "package-lock.json",
        "vitest.config.*",
        "vite.config.*",
        ".github/workflows/**"
      ],
      "probes": {
        "mutation": {
          "file": "src/wicked_mutation.test.js",
          "content": "import { it, expect } from 'vitest';\n\nit('wicked mutation probe', () => {\n  expect(1 + 1).toBe(3);\n});\n",
          "expectId": "wicked mutation probe"
        },
        "mutation2": {
          "file": "src/wicked_mutation_two.test.js",
          "content": "import { it, expect } from 'vitest';\n\nit('wicked mutation probe two', () => {\n  expect(1 + 1).toBe(3);\n});\n",
          "expectId": "wicked mutation probe two"
        }
      }
    }
  ]
}
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall