[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8P6VJHJSZDRVFB6567W1H":3,"skill-same:01M7C8P6VJHJSZDRVFB6567W1H":115},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7C8P6VJHJSZDRVFB6567W1H","create-project-verification-skill",null,"Use for \u002Fcreate-project-verification-skill, \u002Fcreate-project-verification-skill quick, or when asked to set up verification for a repo.","thanostourik\u002Fagent-config","thanostourik","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8533815?v=4","01M7C8NR4FZRHP6XF6FAZH4QXE","Thanos Tourikas","01M7C8NR57G236RMSDVV79N29M",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-project-verification-skill\nmetadata:\n  harness: \"claude-code, codex, grok, cursor\"\ndescription: \"Use for \u002Fcreate-project-verification-skill, \u002Fcreate-project-verification-skill quick, or when asked to set up verification for a repo.\"\ndisable-model-invocation: true\n---\n\n# Create a project verification skill\n\nThis skill gives a project a `verify-\u003Capp>` skill. That skill has an isolated environment,\none bash recipe per feature, and the shipped runner `bin\u002Fverify`, which drives the recipes\nin parallel without an agent. Agents then drive the features a change touches before they\ncall work done. You write for the next agent, which reads the result in the middle of\nanother task, with no other context. Recorders are subagents. Each one writes the recipes\nof one area of the app.\n\n## Modes\n\n- `\u002Fcreate-project-verification-skill` (default): record every feature.\n- `\u002Fcreate-project-verification-skill quick`: write the environment and one recipe, with no\n  recorders. Do steps 1 to 3, steps 4.1 and 4.3, the lifecycle checks of step 5, and\n  step 6. The one recipe proves that the environment, sign-in, the browser helper and\n  cleanup work, and agents copy it. The other recipes grow with the code: `verify affected`\n  fails while a change adds a screen, route or action no recipe covers, `verify uncovered`\n  lists the rest, and `\u002Fverify-\u003Capp> full` records them when the user asks.\n\nA request with the same meaning picks the same mode. Do not ask which mode to use. Keep\nyour own context small: write the environment and the first recipe yourself, and leave the\nother recipes to recorders.\n\nWhen you need me to make a choice before you can continue, use your question tool if you\nhave one, or ask in your reply if you don't. If the question gets no answer, ask again in\nyour reply and wait. Do not answer it yourself.\n\nIf `.agents\u002Fskills\u002Fverify-*` already exists, stop before writing anything. Ask whether to\nreplace it (delete and generate again) or upgrade it with\n`\u002Fmaintain-project-verification-skill`.\n\n`\u003Cgenerator>` below is this skill's folder.\n\n## What you write\n\n```\n.agents\u002Fskills\u002Fverify-\u003Capp>\u002F\n  SKILL.md            \u003Cgenerator>\u002Freferences\u002Fverify-skill.md, with \u003Capp> filled in\n  FULL.md             \u003Cgenerator>\u002Freferences\u002Ffull.md, with \u003Capp> filled in\n  RECORDERS.md        copied from \u003Cgenerator>\u002Freferences\u002Frecorders.md, unchanged\n  PROJECT.md          this project's facts (step 3)\n  bin\u002Fverify          copied from \u003Cgenerator>\u002Freferences\u002Fverify, unchanged\n  bin\u002Flib.sh          copied from \u003Cgenerator>\u002Freferences\u002Flib.sh, unchanged\n  bin\u002Fharvest         copied from \u003Cgenerator>\u002Freferences\u002Fharvest, unchanged\n  bin\u002Fareas           copied from \u003Cgenerator>\u002Freferences\u002Fareas, unchanged (needs python3)\n  bin\u002Freach           copied from \u003Cgenerator>\u002Freferences\u002Freach, unchanged (needs python3)\n  bin\u002Fpw.sh bin\u002Fpw-close   copied from \u003Cgenerator>\u002Freferences, unchanged, for a web UI; pw-version beside SKILL.md\n  bin\u002Flaunch.sh bin\u002Fcleanup.sh bin\u002Fdoctor.sh bin\u002Fobserve.sh bin\u002Fserver-errors.sh\n  bin\u002Fenv.sh bin\u002Fafter-feature.sh   optional\n  bin\u002Fentrypoints.sh bin\u002Factions.sh\n  bin\u002F\u003Cdriver helpers>\n  features\u002F\u003Cfeature>.sh\n  .gitignore          holds .cache\u002F\n  apps                companion repo only\n.claude\u002Fskills\u002Fverify-\u003Capp>\u002FSKILL.md   stub from \u003Cgenerator>\u002Freferences\u002Fclaude-stub.md\n.claude\u002Fsettings.json                  \"Bash(sudo:*)\" merged into permissions.deny\n```\n\n`\u003Capp>` is a short lowercase name. Codex, Cursor, Grok and OpenCode read `.agents\u002Fskills\u002F`.\nClaude Code reads only `.claude\u002Fskills\u002F`, so the stub exists for it. Never use symlinks.\n\n`SKILL.md`, `FULL.md` and the files marked `unchanged` are the shipped files. An upgrade replaces\nthem, so never edit them for the project. Everything project-specific goes into\n`PROJECT.md`, the other `bin\u002F` helpers and `features\u002F`.\n\n## Companion repo\n\nSome projects must not show that agents work on them. Their skill lives in a companion\nrepo: a separate git repo next to the app checkouts that holds only agent files.\n\nRun one `git ls-files` here. When it lists no app source, this is a companion:\n\n- Ask for the path of each app checkout. Write `.agents\u002Fskills\u002Fverify-\u003Capp>\u002Fapps` with one\n  line `\u003Cname> \u003Cpath>` per app, the path relative to this repo's root.\n- `bin\u002Fverify` exports each path as `APP_\u003CNAME>` (upper case, `-` as `_`). A value the\n  caller set wins.\n- Recipes, `# touches:` lines and helpers name app files as `\u003Cname>\u002F\u003Cpath>` and reach them\n  through `$APP_\u003CNAME>`.\n\nNothing goes into an app checkout: no file, no dependency, no build output. Build from a\ncopy under `.cache\u002F`, or send build output outside the checkout. Run git against a checkout\nwith `GIT_OPTIONAL_LOCKS=0`. Report a checkout that does not build; do not fix it.\nPlaywright, when needed, goes into the companion's own `package.json`.\n\n## 1. Read the repo\n\nAnswer from the codebase. Ask only what you cannot observe.\n\n- **Surfaces:** web UI, API, CLI or TUI, desktop, mobile, firmware, jobs.\n- **Run:** how the app starts locally, its dependencies, ports, seed data and sign-in.\n- **Harness:** existing end-to-end specs, sign-in or seed helpers, curl-able endpoints.\n- **Entry points:** the files that define routes, screens, commands or endpoints, found\n  with one grep. That grep becomes `bin\u002Fentrypoints.sh`.\n- **Checks:** the focused test, lint and type-check commands.\n- **Sibling repos:** another repo the app needs at run time, such as a backend. Use the path\n  its docs name, else `..\u002F\u003Cname>`, and write it into `PROJECT.md`.\n\nIf the app does not build or start as it is, fix that or report it before going on.\n\n## 2. Isolation\n\nChoose the isolation level once, following\n[`references\u002Flifecycle.md`](references\u002Flifecycle.md): `full` (default), `shared` or\n`checks-only`. That file also says which ports a run may use and how to use\n`local-stack\u002Fstack`. Ask the user only when `full` is not possible. Recipes read every URL\nand port from `env.sh`, never `localhost:\u003Cdefault>`.\n\n## 3. Write the environment and `PROJECT.md`\n\nAt level `checks-only` the app cannot run, so there is no environment to write. Do only\nthis, then go to step 6: write `PROJECT.md` with the focused checks, copy the shipped files\nas the tree above shows, and write the Claude stub and `.gitignore`. Write no environment\nscripts and no recipes, and launch nothing.\n\nAt the other levels, write the scripts below into `bin\u002F` and make each one executable.\n\n### Environment scripts\n\n- `launch.sh` creates and starts the run's environment. It registers each resource as it\n  creates it, and waits until the environment is ready, with a deadline.\n  - `$VERIFY_RUN_ID` names the run and stays the same until `bin\u002Fverify down`.\n  - With `VERIFY_APP=dev` it runs the app with the developers' own dev command, such as\n    `next dev` or `.\u002Fmvnw spring-boot:run`, as a process the run records. A code change\n    then needs no image build.\n  - With `VERIFY_APP=build` it runs the production build.\n  - A run uses `dev` unless its first `bin\u002Fverify up` sets `VERIFY_APP=build`. `verify all`\n    and lanes always use `build`.\n  - It is idempotent. When the run's environment already exists, it restarts the app, so a\n    second `bin\u002Fverify up` takes seconds.\n- `cleanup.sh` removes only what the run created, after success, failure and interruption,\n  and checks that none of it remains. It never checks resources that existed before. With\n  no run recorded, it exits 0.\n- `env.sh` (optional) exports the run's values that recipes and helpers need, such as base\n  URLs, ports and keys. It reads them from the run's record. The runner sources it before\n  each recipe.\n- `after-feature.sh` (optional) runs after every recipe's `cleanup`, for example to close\n  the feature's browser session. A finished feature then holds nothing until\n  `bin\u002Fverify down`.\n- `doctor.sh` is one fast, read-only check that the environment belongs to this run and is\n  healthy: processes up, right checkout, ports owned, sign-in works. It never treats a\n  process outside the run's record as the run's.\n- `observe.sh \u003Cpath>` saves the app's current state for a failed step: the snapshot or\n  screenshot of the feature's browser session (`$VERIFY_SESSION`), the last HTTP response,\n  or the last command output.\n- `server-errors.sh \u003Cepoch seconds>`, for an app with a server, prints the errors the\n  server logged since that time, each with its stack trace. It prints nothing when there\n  are none.\n  - It reads the errors where this stack writes them, such as `docker logs --since` for a\n    container, the app server's log file, or the output of the dev process the run\n    records. It reads the copy that `$VERIFY_RUN_ID` names.\n  - The summary line shows only the first line, so start each error with the request and\n    the exception.\n  - When a step fails, `lib.sh` calls it with the time the step began and saves its output\n    as evidence. A UI timeout caused by a server error then explains itself.\n  - A failed `bin\u002Fverify up` calls it too, with the time the launch began. So it must also\n    work on a run whose app never became ready, such as one that stopped at a migration.\n  - Check it once by causing a server error, such as a request the app answers with\n    HTTP 500.\n\n### Scripts that list what to cover\n\n- `entrypoints.sh` prints every entry point, one per line, as `\u003Centry point>\u003CTAB>\u003Cfile>`:\n  a route with its method (`POST \u002Fapi\u002Fnotes`), a screen's path, a command (`todo add`), a\n  job or message handler.\n  - It searches the source, such as route annotations or a router file, so it finds new\n    entry points by itself.\n  - Some frameworks build entry points at run time, from configuration or the database,\n    where no source search finds them. When the project's framework is in\n    [`references\u002Fdiscovery.md`](references\u002Fdiscovery.md), list them the way it says.\n  - List only what a user or client calls: not update or deploy hooks, migrations, compose\n    services or schemas.\n  - `bin\u002Fverify uncovered` compares its output with the recipes' `# covers:` lines.\n- `actions.sh` prints every user action, one per line, as `\u003Cname>\u003CTAB>\u003Cfile>`: each\n  function a screen runs when the user acts (event handlers such as `handleDelete`, form\n  submits). For a project without a UI, it prints each handler method behind an entry\n  point. It searches the source, like `entrypoints.sh`.\n  - Name an inline handler (`onClick={() => remove(id)}`) after its element's label or test\n    id, such as `Delete button`. Never use a line number: it changes whenever the file\n    shifts.\n  - A screen can get a handler from a hook or a parent\n    (`const { start } = useDeviceControl()`). List it under the screen's file too. A search\n    for `const handle...` alone misses it.\n  - `bin\u002Fverify uncovered` lists each action that no recipe's `# expects:` line cites by\n    its file and name. `bin\u002Fverify affected` lists those in changed files.\n\n### Rules for every helper\n\n- A helper also works when an agent calls it by hand, outside `bin\u002Fverify`. It sets\n  `: \"${VERIFY_SKILL:=$(cd \"$(dirname \"$0\")\u002F..\" && pwd)}\"` and gives the other `VERIFY_*`\n  variables it reads a default.\n- Its waits and error output follow the \"Waits and errors\" rules in the shipped `SKILL.md`.\n  A helper that inserts rows directly follows the fixture rule in that file's Data section.\n  `verify lint` checks only recipes, so check helpers yourself.\n- A helper that runs a command inside a container passes environment overrides through\n  (`bin\u002Fcli -e KEY=VALUE \u003Ccommand>`). A recipe can then point one command at its own\n  schema, prefix or folder.\n\n### Driver helpers\n\nA driver helper that keeps state keeps it per `$VERIFY_SESSION`.\n\nFor a web UI without its own harness:\n\n- Copy `pw.sh` and `pw-close` to `bin\u002F` unchanged. The header of `pw.sh` says how to call\n  it.\n- Write into the skill's `pw-version` file a Playwright version whose browser build is\n  installed (`ls ~\u002F.cache\u002Fms-playwright`). `pw.sh` installs that version under `.cache\u002F` on\n  first use.\n- `after-feature.sh` runs `bin\u002Fpw-close feature`, and `cleanup.sh` runs `bin\u002Fpw-close run`.\n  No recorder calls `pw-close`, because other drives share the run's browser.\n\nThen write:\n\n- A sign-in helper. It saves each account's storage state once per run and loads it in one\n  call. It signs each account into a browser session of its own: a second account in the\n  same session is signed in as the first, through the sign-in provider's cookie.\n- Account helpers. Creating or deleting an account also removes that account's cached state\n  and token.\n- Every cached file (token, storage state) through a temporary file of its own (`mktemp` in\n  the same folder) and `mv`. Features sign in at the same time, and a shared temporary name\n  makes one feature's `mv` fail.\n\nFor an API, an `api` helper wraps `curl` with the base URL, auth and `--max-time`, and\nsaves the last response for `observe.sh`.\n\n### `PROJECT.md`\n\nWrite `PROJECT.md`, about 10 KB, with these sections:\n\n- **Drivers:** the tools that drive the app, such as `Playwright CLI and curl`, and why.\n- **Isolation:** `Isolation level: \u003Clevel>`, one line on why, what the run owns and its\n  markers, and the success paths the isolation cannot reach (such as a real payment that a\n  stub replaces).\n- **Environment:** what `launch.sh`, `cleanup.sh` and `doctor.sh` do, and how long a first\n  and a second `bin\u002Fverify up` take.\n- **Sign-in and data:** the test accounts and baseline data a recipe can count on, each\n  checked with one command against the running environment.\n- **Stubs:** for each stub or fake service in the run, what it returns and stores and what\n  it cannot do (such as an ML stub that stores nothing, or a collector that returns no\n  data), each checked with one call. Recorders read this instead of finding it out in\n  failed runs.\n- **Helpers:** one line per helper with one real call as a recipe writes it, what it checks\n  or returns, and its deadline when it waits.\n- **Focused checks:** the test, lint and type-check commands.\n- **Gotchas:** traps that hold for several features, one line each with the fix. A trap of\n  one feature goes in that recipe's header instead. Start with the driver's traps. For the\n  Playwright CLI:\n  - After a click that navigates, wait for the new URL or state before the next check.\n  - After `goto` or `reload`, wait for an element only the client renders before the first\n    click. A click before the page is interactive does nothing.\n  - A `confirm()` dialog blocks every command until it is handled.\n  - A role name matches as a substring unless `exact: true`.\n  - The `run-code` function runs in a bare sandbox. Node and browser globals such as `URL`,\n    `require` and `console` are not there, so parse URLs and log inside `page.evaluate`, or\n    return the value.\n\n### Bring it up\n\n1. Copy the shipped files as the tree above shows, and write the Claude stub and\n   `.gitignore`.\n2. Run `VERIFY_APP=build bin\u002Fverify up` in the background. While it builds, do the parts of\n   step 4 that come before the first recipe.\n3. Run `bin\u002Fverify up` again, which keeps the production build. Time both calls.\n\nGeneration uses the production build. A dev server holds far more memory, and with many\nfeatures at once it loses clicks that land before a page is ready. The first `up` also\nmeasures how much memory and time one copy of the environment takes. The runner needs both\nto decide on lanes (extra copies of the environment for `# alone` features).\n\nFor a CLI or a library there is no process to restart. `launch.sh` prepares the run's data\nfolder and builds once, and `doctor.sh` checks that the folder is the run's and the build is\ncurrent.\n\n### Build the environment for speed\n\nEvery recipe waits on the environment in every run.\n\n- Derive every per-run file name and port from `$VERIFY_RUN_ID`, never a fixed path such as\n  `.cache\u002Frun\u002F`, so lanes can run side by side.\n- Shorten every timer the features wait on, in the run's own configuration: job intervals,\n  retry delays, grace periods, expiries, polling.\n  - When the project's stack fixes the environment and offers no way to override it, add\n    one to the stack as part of the repo, such as a compose override file it reads. Or note\n    the gap and start the job once per recipe.\n  - Write each override and the recipes that rely on it into `PROJECT.md`.\n  - Before shortening a job for all features, check which recipes set up the state that job\n    consumes.\n- Keep each copy small so lanes fit in memory. Cap worker counts and heap sizes: a JVM\n  without `-Xmx` takes a quarter of the machine. Start the project's own JVM apps with\n  `-XX:TieredStopAtLevel=1 -XX:+UseSerialGC`, which shortens startup.\n- Give every service of the run a memory limit (`mem_limit` for a container), third-party\n  ones included. Step 4.3 sizes it, once the example recipe passes.\n  - A runtime that sizes its heap from the container, such as a JVM, then stays inside it.\n  - Change only the limit of a third-party service, never its startup flags. Keycloak's\n    start script picks a garbage collector that clashes with `UseSerialGC`, and then\n    Keycloak does not start.\n  - When the services come from the project's local stack, the limit goes into that stack\n    (`create-project-local-stack`), not into the run.\n- A stub or helper that starts a process first stops any leftover of the same feature, so\n  an interrupted run never blocks the next one.\n- Lanes share one build. Build images or artifacts once, under a lock, and let every lane\n  start from them. Only when the build bakes ports into an image (such as `NEXT_PUBLIC_*`\n  URLs) does each lane build its own.\n- `launch.sh` and every helper that restarts the app, such as for a clock shift, wait until\n  a real page answers, signed in where the app has sign-in, as \"Waits and errors\" says.\n  They poll every half second and never run the whole doctor.\n- `cleanup.sh` stops throwaway containers without a grace period\n  (`docker compose down -t 1`).\n- `doctor.sh` retries each probe a few times with a 30 s limit, so a loaded machine never\n  stops a drive with a false failure.\n\n## 4. Record every feature\n\n1. Run `bin\u002Fareas > .cache\u002Fareas.txt`. It groups the entry points into areas of about 1,000\n   lines of source, one line per area:\n   `\u003Carea>: \u003Cn> lines; entry points: \u003C...>; files: \u003C...>`. The files are the entry points'\n   folders and the project files they import. One recorder records one area. Review the\n   file:\n   - Leave a line marked `split:` as it is. It is one file over the size, and its recorder\n     takes longer.\n   - Rename an area whose name does not say what the user calls the screen, such as one\n     named `area2-\u003Cname>`.\n   - Move a file the lines miss, such as a component two screens share, to the area that\n     uses it most.\n   - Make sure no area name equals another or starts with another followed by `-`. Features\n     are named `\u003Carea>-\u003Cgoal>`, and `bin\u002Fverify uncovered \u003Carea>` finds an area's features\n     by that prefix.\n\n   Do not name features. Each recorder lists every behavior of its area from the source and\n   splits that list into features itself.\n2. Write each area's expectation list, as the Expectation lists section of the copied\n   `FULL.md` says.\n3. Write the first recipe yourself, for the simplest feature. Follow the Recipes section of\n   the copied `SKILL.md`, and name the recipe `\u003Carea>-\u003Cgoal>` after its area. That area's\n   recorder keeps it. Run `bin\u002Fverify \u003Cfeature>` until it passes. Every recorder copies\n   this recipe as its example, so make it clean. Then:\n   - Drive the main create path by hand once: create the same record twice, and read it as\n     a second tenant or user. Write what that shows about ids, uniqueness and shared data\n     into `PROJECT.md`'s Gotchas before any recorder starts, so no recorder hits the same\n     trap.\n   - Write the setup helpers several features need, such as signing in as each role,\n     creating an account with a role, provisioning a subscription or workspace, adding a\n     member, or reading the run's mail.\n   - Write the fixture helper for each row several features insert directly, such as a\n     user (the Data section's rule for such rows), before any recorder writes that insert\n     into a recipe.\n   - Call each helper once the way a recipe calls it, after deleting its cached state (such\n     as saved sign-ins), so its slow path runs too. A cache can hide a wrong argument until\n     the first fresh drive.\n   - Size each service's memory limit: about one and a half times what the service uses\n     after a busy run. A busy run is the example recipe's flow plus a few hundred sign-ins,\n     30 at a time. Read the use with `docker stats`. Never size the limit from an idle\n     stack.\n4. Run `bin\u002Fverify up --lanes 1`. A feature marked `# alone` waits until its copy is free\n   of other features, so on a single copy every other drive stops meanwhile. With the extra\n   copy, every drive runs its `# alone` features there instead. Then start recorders as the\n   Recorders section of the copied `FULL.md` says: one per area, every area at once,\n   heaviest first.\n5. Read only their result files. Add their traps to `PROJECT.md`'s Gotchas.\n\n## 5. Prove it\n\nRun `bin\u002Fverify down`. Then do steps 2 to 5 of Full in the copied `FULL.md`. Its first\n`verify all` starts a fresh environment on the production build, so every recipe runs once\nmore with every other feature beside it. Send a failing feature, an uncovered line or a\nnot-driven reason that does not hold back to the recorder that recorded its area, instead\nof starting a new one. In the final `verify all`, every feature runs on an environment\nwhere it already ran, which also proves each recipe repeats.\n\nThe runner starts up to as many features at once as the machine has cores, each only when\nthe machine-wide queue has room. Write a `jobs` file only when the project needs a lower\nlimit, such as a service with few connections. When `# alone` features remain, write into\nthe skill's `lanes` file the most extra copies a drive may start: about their total time\ndivided by the longest parallel feature.\n\nThen check the lifecycle once:\n\n- Run `bin\u002Fverify lint`. Fix every `# expects:` line it lists as citing code the checkouts\n  do not have: `bin\u002Fverify affected` can never select a feature through such a line.\n- Commit, change one line in a function that an `# expects:` line cites, and check that\n  `bin\u002Fverify affected --dry --base HEAD` lists that feature under \"Check the edited\n  code\". Without `--base HEAD` on this branch, every new recipe counts as changed. Undo\n  the change. In a companion, change a copy of the app checkout instead and point\n  `APP_\u003CNAME>` at it.\n- Check that `bin\u002Fverify down` leaves nothing of the run outside `.cache\u002F`: no process,\n  port, container, browser session or file.\n\n## 6. Instructions and hand-over\n\nWrite one `## Verification` section in the project's `AGENTS.md` from\n[`references\u002Fagents-verification.md`](references\u002Fagents-verification.md), with `\u003Capp>` and\nthe focused check commands filled in. In a companion repo it goes in the companion's\n`AGENTS.md`. Create the file when there is none.\n\n- Integrate an existing verification section instead of adding a second one. Rewrite a\n  section that points at a verify skill this run replaces.\n- If there is no `CLAUDE.md`, create one holding only `@AGENTS.md`. If one exists without\n  that import, put the same section there too.\n- Replace agent instructions for launching the app by hand with a pointer to the skill.\n  Leave the README's instructions for people.\n- Report an older verification system instead of deleting it.\n\nMerge `Bash(sudo:*)` into `permissions.deny` of `.claude\u002Fsettings.json`, keeping the rest.\nCommit following the repo's conventions. Report: the isolation level, how long recording and\n`bin\u002Fverify all` took, one line per feature (pass, fail with its kind, or blocked with what\nwas tried), and product defects found.\n","# Create a project verification skill\n\nThis skill gives a project a `verify-\u003Capp>` skill. That skill has an isolated environment,\none bash recipe per feature, and the shipped runner `bin\u002Fverify`, which drives the recipes\nin parallel without an agent. Agents then drive the features a change touches before they\ncall work done. You write for the next agent, which reads the result in the middle of\nanother task, with no other context. Recorders are subagents. Each one writes the recipes\nof one area of the app.\n\n## Modes\n\n- `\u002Fcreate-project-verification-skill` (default): record every feature.\n- `\u002Fcreate-project-verification-skill quick`: write the environment and one recipe, with no\n  recorders. Do steps 1 to 3, steps 4.1 and 4.3, the lifecycle checks of step 5, and\n  step 6. The one recipe proves that the environment, sign-in, the browser helper and\n  cleanup work, and agents copy it. The other recipes grow with the code: `verify affected`\n  fails while a change adds a screen, route or action no recipe covers, `verify uncovered`\n  lists the rest, and `\u002Fverify-\u003Capp> full` records them when the user asks.\n\nA request with the same meaning picks the same mode. Do not ask which mode to use. Keep\nyour own context small: write the environment and the first recipe yourself, and leave the\nother recipes to recorders.\n\nWhen you need me to make a choice before you can continue, use your question tool if you\nhave one, or ask in your reply if you don't. If the question gets no answer, ask again in\nyour reply and wait. Do not answer it yourself.\n\nIf `.agents\u002Fskills\u002Fverify-*` already exists, stop before writing anything. Ask whether to\nreplace it (delete and generate again) or upgrade it with\n`\u002Fmaintain-project-verification-skill`.\n\n`\u003Cgenerator>` below is this skill's folder.\n\n## What you write\n\n```\n.agents\u002Fskills\u002Fverify-\u003Capp>\u002F\n  SKILL.md            \u003Cgenerator>\u002Freferences\u002Fverify-skill.md, with \u003Capp> filled in\n  FULL.md             \u003Cgenerator>\u002Freferences\u002Ffull.md, with \u003Capp> filled in\n  RECORDERS.md        copied from \u003Cgenerator>\u002Freferences\u002Frecorders.md, unchanged\n  PROJECT.md          this project's facts (step 3)\n  bin\u002Fverify          copied from \u003Cgenerator>\u002Freferences\u002Fverify, unchanged\n  bin\u002Flib.sh          copied from \u003Cgenerator>\u002Freferences\u002Flib.sh, unchanged\n  bin\u002Fharvest         copied from \u003Cgenerator>\u002Freferences\u002Fharvest, unchanged\n  bin\u002Fareas           copied from \u003Cgenerator>\u002Freferences\u002Fareas, unchanged (needs python3)\n  bin\u002Freach           copied from \u003Cgenerator>\u002Freferences\u002Freach, unchanged (needs python3)\n  bin\u002Fpw.sh bin\u002Fpw-close   copied from \u003Cgenerator>\u002Freferences, unchanged, for a web UI; pw-version beside SKILL.md\n  bin\u002Flaunch.sh bin\u002Fcleanup.sh bin\u002Fdoctor.sh bin\u002Fobserve.sh bin\u002Fserver-errors.sh\n  bin\u002Fenv.sh bin\u002Fafter-feature.sh   optional\n  bin\u002Fentrypoints.sh bin\u002Factions.sh\n  bin\u002F\u003Cdriver helpers>\n  features\u002F\u003Cfeature>.sh\n  .gitignore          holds .cache\u002F\n  apps                companion repo only\n.claude\u002Fskills\u002Fverify-\u003Capp>\u002FSKILL.md   stub from \u003Cgenerator>\u002Freferences\u002Fclaude-stub.md\n.claude\u002Fsettings.json                  \"Bash(sudo:*)\" merged into permissions.deny\n```\n\n`\u003Capp>` is a short lowercase name. Codex, Cursor, Grok and OpenCode read `.agents\u002Fskills\u002F`.\nClaude Code reads only `.claude\u002Fskills\u002F`, so the stub exists for it. Never use symlinks.\n\n`SKILL.md`, `FULL.md` and the files marked `unchanged` are the shipped files. An upgrade replaces\nthem, so never edit them for the project. Everything project-specific goes into\n`PROJECT.md`, the other `bin\u002F` helpers and `features\u002F`.\n\n## Companion repo\n\nSome projects must not show that agents work on them. Their skill lives in a companion\nrepo: a separate git repo next to the app checkouts that holds only agent files.\n\nRun one `git ls-files` here. When it lists no app source, this is a companion:\n\n- Ask for the path of each app checkout. Write `.agents\u002Fskills\u002Fverify-\u003Capp>\u002Fapps` with one\n  line `\u003Cname> \u003Cpath>` per app, the path relative to this repo's root.\n- `bin\u002Fverify` exports each path as `APP_\u003CNAME>` (upper case, `-` as `_`). A value the\n  caller set wins.\n- Recipes, `# touches:` lines and helpers name app files as `\u003Cname>\u002F\u003Cpath>` and reach them\n  through `$APP_\u003CNAME>`.\n\nNothing goes into an app checkout: no file, no dependency, no build output. Build from a\ncopy under `.cache\u002F`, or send build output outside the checkout. Run git against a checkout\nwith `GIT_OPTIONAL_LOCKS=0`. Report a checkout that does not build; do not fix it.\nPlaywright, when needed, goes into the companion's own `package.json`.\n\n## 1. Read the repo\n\nAnswer from the codebase. Ask only what you cannot observe.\n\n- **Surfaces:** web UI, API, CLI or TUI, desktop, mobile, firmware, jobs.\n- **Run:** how the app starts locally, its dependencies, ports, seed data and sign-in.\n- **Harness:** existing end-to-end specs, sign-in or seed helpers, curl-able endpoints.\n- **Entry points:** the files that define routes, screens, commands or endpoints, found\n  with one grep. That grep becomes `bin\u002Fentrypoints.sh`.\n- **Checks:** the focused test, lint and type-check commands.\n- **Sibling repos:** another repo the app needs at run time, such as a backend. Use the path\n  its docs name, else `..\u002F\u003Cname>`, and write it into `PROJECT.md`.\n\nIf the app does not build or start as it is, fix that or report it before going on.\n\n## 2. Isolation\n\nChoose the isolation level once, following\n[`references\u002Flifecycle.md`](references\u002Flifecycle.md): `full` (default), `shared` or\n`checks-only`. That file also says which ports a run may use and how to use\n`local-stack\u002Fstack`. Ask the user only when `full` is not possible. Recipes read every URL\nand port from `env.sh`, never `localhost:\u003Cdefault>`.\n\n## 3. Write the environment and `PROJECT.md`\n\nAt level `checks-only` the app cannot run, so there is no environment to write. Do only\nthis, then go to step 6: write `PROJECT.md` with the focused checks, copy the shipped files\nas the tree above shows, and write the Claude stub and `.gitignore`. Write no environment\nscripts and no recipes, and launch nothing.\n\nAt the other levels, write the scripts below into `bin\u002F` and make each one executable.\n\n### Environment scripts\n\n- `launch.sh` creates and starts the run's environment. It registers each resource as it\n  creates it, and waits until the environment is ready, with a deadline.\n  - `$VERIFY_RUN_ID` names the run and stays the same until `bin\u002Fverify down`.\n  - With `VERIFY_APP=dev` it runs the app with the developers' own dev command, such as\n    `next dev` or `.\u002Fmvnw spring-boot:run`, as a process the run records. A code change\n    then needs no image build.\n  - With `VERIFY_APP=build` it runs the production build.\n  - A run uses `dev` unless its first `bin\u002Fverify up` sets `VERIFY_APP=build`. `verify all`\n    and lanes always use `build`.\n  - It is idempotent. When the run's environment already exists, it restarts the app, so a\n    second `bin\u002Fverify up` takes seconds.\n- `cleanup.sh` removes only what the run created, after success, failure and interruption,\n  and checks that none of it remains. It never checks resources that existed before. With\n  no run recorded, it exits 0.\n- `env.sh` (optional) exports the run's values that recipes and helpers need, such as base\n  URLs, ports and keys. It reads them from the run's record. The runner sources it before\n  each recipe.\n- `after-feature.sh` (optional) runs after every recipe's `cleanup`, for example to close\n  the feature's browser session. A finished feature then holds nothing until\n  `bin\u002Fverify down`.\n- `doctor.sh` is one fast, read-only check that the environment belongs to this run and is\n  healthy: processes up, right checkout, ports owned, sign-in works. It never treats a\n  process outside the run's record as the run's.\n- `observe.sh \u003Cpath>` saves the app's current state for a failed step: the snapshot or\n  screenshot of the feature's browser session (`$VERIFY_SESSION`), the last HTTP response,\n  or the last command output.\n- `server-errors.sh \u003Cepoch seconds>`, for an app with a server, prints the errors the\n  server logged since that time, each with its stack trace. It prints nothing when there\n  are none.\n  - It reads the errors where this stack writes them, such as `docker logs --since` for a\n    container, the app server's log file, or the output of the dev process the run\n    records. It reads the copy that `$VERIFY_RUN_ID` names.\n  - The summary line shows only the first line, so start each error with the request and\n    the exception.\n  - When a step fails, `lib.sh` calls it with the time the step began and saves its output\n    as evidence. A UI timeout caused by a server error then explains itself.\n  - A failed `bin\u002Fverify up` calls it too, with the time the launch began. So it must also\n    work on a run whose app never became ready, such as one that stopped at a migration.\n  - Check it once by causing a server error, such as a request the app answers with\n    HTTP 500.\n\n### Scripts that list what to cover\n\n- `entrypoints.sh` prints every entry point, one per line, as `\u003Centry point>\u003CTAB>\u003Cfile>`:\n  a route with its method (`POST \u002Fapi\u002Fnotes`), a screen's path, a command (`todo add`), a\n  job or message handler.\n  - It searches the source, such as route annotations or a router file, so it finds new\n    entry points by itself.\n  - Some frameworks build entry points at run time, from configuration or the database,\n    where no source search finds them. When the project's framework is in\n    [`references\u002Fdiscovery.md`](references\u002Fdiscovery.md), list them the way it says.\n  - List only what a user or client calls: not update or deploy hooks, migrations, compose\n    services or schemas.\n  - `bin\u002Fverify uncovered` compares its output with the recipes' `# covers:` lines.\n- `actions.sh` prints every user action, one per line, as `\u003Cname>\u003CTAB>\u003Cfile>`: each\n  function a screen runs when the user acts (event handlers such as `handleDelete`, form\n  submits). For a project without a UI, it prints each handler method behind an entry\n  point. It searches the source, like `entrypoints.sh`.\n  - Name an inline handler (`onClick={() => remove(id)}`) after its element's label or test\n    id, such as `Delete button`. Never use a line number: it changes whenever the file\n    shifts.\n  - A screen can get a handler from a hook or a parent\n    (`const { start } = useDeviceControl()`). List it under the screen's file too. A search\n    for `const handle...` alone misses it.\n  - `bin\u002Fverify uncovered` lists each action that no recipe's `# expects:` line cites by\n    its file and name. `bin\u002Fverify affected` lists those in changed files.\n\n### Rules for every helper\n\n- A helper also works when an agent calls it by hand, outside `bin\u002Fverify`. It sets\n  `: \"${VERIFY_SKILL:=$(cd \"$(dirname \"$0\")\u002F..\" && pwd)}\"` and gives the other `VERIFY_*`\n  variables it reads a default.\n- Its waits and error output follow the \"Waits and errors\" rules in the shipped `SKILL.md`.\n  A helper that inserts rows directly follows the fixture rule in that file's Data section.\n  `verify lint` checks only recipes, so check helpers yourself.\n- A helper that runs a command inside a container passes environment overrides through\n  (`bin\u002Fcli -e KEY=VALUE \u003Ccommand>`). A recipe can then point one command at its own\n  schema, prefix or folder.\n\n### Driver helpers\n\nA driver helper that keeps state keeps it per `$VERIFY_SESSION`.\n\nFor a web UI without its own harness:\n\n- Copy `pw.sh` and `pw-close` to `bin\u002F` unchanged. The header of `pw.sh` says how to call\n  it.\n- Write into the skill's `pw-version` file a Playwright version whose browser build is\n  installed (`ls ~\u002F.cache\u002Fms-playwright`). `pw.sh` installs that version under `.cache\u002F` on\n  first use.\n- `after-feature.sh` runs `bin\u002Fpw-close feature`, and `cleanup.sh` runs `bin\u002Fpw-close run`.\n  No recorder calls `pw-close`, because other drives share the run's browser.\n\nThen write:\n\n- A sign-in helper. It saves each account's storage state once per run and loads it in one\n  call. It signs each account into a browser session of its own: a second account in the\n  same session is signed in as the first, through the sign-in provider's cookie.\n- Account helpers. Creating or deleting an account also removes that account's cached state\n  and token.\n- Every cached file (token, storage state) through a temporary file of its own (`mktemp` in\n  the same folder) and `mv`. Features sign in at the same time, and a shared temporary name\n  makes one feature's `mv` fail.\n\nFor an API, an `api` helper wraps `curl` with the base URL, auth and `--max-time`, and\nsaves the last response for `observe.sh`.\n\n### `PROJECT.md`\n\nWrite `PROJECT.md`, about 10 KB, with these sections:\n\n- **Drivers:** the tools that drive the app, such as `Playwright CLI and curl`, and why.\n- **Isolation:** `Isolation level: \u003Clevel>`, one line on why, what the run owns and its\n  markers, and the success paths the isolation cannot reach (such as a real payment that a\n  stub replaces).\n- **Environment:** what `launch.sh`, `cleanup.sh` and `doctor.sh` do, and how long a first\n  and a second `bin\u002Fverify up` take.\n- **Sign-in and data:** the test accounts and baseline data a recipe can count on, each\n  checked with one command against the running environment.\n- **Stubs:** for each stub or fake service in the run, what it returns and stores and what\n  it cannot do (such as an ML stub that stores nothing, or a collector that returns no\n  data), each checked with one call. Recorders read this instead of finding it out in\n  failed runs.\n- **Helpers:** one line per helper with one real call as a recipe writes it, what it checks\n  or returns, and its deadline when it waits.\n- **Focused checks:** the test, lint and type-check commands.\n- **Gotchas:** traps that hold for several features, one line each with the fix. A trap of\n  one feature goes in that recipe's header instead. Start with the driver's traps. For the\n  Playwright CLI:\n  - After a click that navigates, wait for the new URL or state before the next check.\n  - After `goto` or `reload`, wait for an element only the client renders before the first\n    click. A click before the page is interactive does nothing.\n  - A `confirm()` dialog blocks every command until it is handled.\n  - A role name matches as a substring unless `exact: true`.\n  - The `run-code` function runs in a bare sandbox. Node and browser globals such as `URL`,\n    `require` and `console` are not there, so parse URLs and log inside `page.evaluate`, or\n    return the value.\n\n### Bring it up\n\n1. Copy the shipped files as the tree above shows, and write the Claude stub and\n   `.gitignore`.\n2. Run `VERIFY_APP=build bin\u002Fverify up` in the background. While it builds, do the parts of\n   step 4 that come before the first recipe.\n3. Run `bin\u002Fverify up` again, which keeps the production build. Time both calls.\n\nGeneration uses the production build. A dev server holds far more memory, and with many\nfeatures at once it loses clicks that land before a page is ready. The first `up` also\nmeasures how much memory and time one copy of the environment takes. The runner needs both\nto decide on lanes (extra copies of the environment for `# alone` features).\n\nFor a CLI or a library there is no process to restart. `launch.sh` prepares the run's data\nfolder and builds once, and `doctor.sh` checks that the folder is the run's and the build is\ncurrent.\n\n### Build the environment for speed\n\nEvery recipe waits on the environment in every run.\n\n- Derive every per-run file name and port from `$VERIFY_RUN_ID`, never a fixed path such as\n  `.cache\u002Frun\u002F`, so lanes can run side by side.\n- Shorten every timer the features wait on, in the run's own configuration: job intervals,\n  retry delays, grace periods, expiries, polling.\n  - When the project's stack fixes the environment and offers no way to override it, add\n    one to the stack as part of the repo, such as a compose override file it reads. Or note\n    the gap and start the job once per recipe.\n  - Write each override and the recipes that rely on it into `PROJECT.md`.\n  - Before shortening a job for all features, check which recipes set up the state that job\n    consumes.\n- Keep each copy small so lanes fit in memory. Cap worker counts and heap sizes: a JVM\n  without `-Xmx` takes a quarter of the machine. Start the project's own JVM apps with\n  `-XX:TieredStopAtLevel=1 -XX:+UseSerialGC`, which shortens startup.\n- Give every service of the run a memory limit (`mem_limit` for a container), third-party\n  ones included. Step 4.3 sizes it, once the example recipe passes.\n  - A runtime that sizes its heap from the container, such as a JVM, then stays inside it.\n  - Change only the limit of a third-party service, never its startup flags. Keycloak's\n    start script picks a garbage collector that clashes with `UseSerialGC`, and then\n    Keycloak does not start.\n  - When the services come from the project's local stack, the limit goes into that stack\n    (`create-project-local-stack`), not into the run.\n- A stub or helper that starts a process first stops any leftover of the same feature, so\n  an interrupted run never blocks the next one.\n- Lanes share one build. Build images or artifacts once, under a lock, and let every lane\n  start from them. Only when the build bakes ports into an image (such as `NEXT_PUBLIC_*`\n  URLs) does each lane build its own.\n- `launch.sh` and every helper that restarts the app, such as for a clock shift, wait until\n  a real page answers, signed in where the app has sign-in, as \"Waits and errors\" says.\n  They poll every half second and never run the whole doctor.\n- `cleanup.sh` stops throwaway containers without a grace period\n  (`docker compose down -t 1`).\n- `doctor.sh` retries each probe a few times with a 30 s limit, so a loaded machine never\n  stops a drive with a false failure.\n\n## 4. Record every feature\n\n1. Run `bin\u002Fareas > .cache\u002Fareas.txt`. It groups the entry points into areas of about 1,000\n   lines of source, one line per area:\n   `\u003Carea>: \u003Cn> lines; entry points: \u003C...>; files: \u003C...>`. The files are the entry points'\n   folders and the project files they import. One recorder records one area. Review the\n   file:\n   - Leave a line marked `split:` as it is. It is one file over the size, and its recorder\n     takes longer.\n   - Rename an area whose name does not say what the user calls the screen, such as one\n     named `area2-\u003Cname>`.\n   - Move a file the lines miss, such as a component two screens share, to the area that\n     uses it most.\n   - Make sure no area name equals another or starts with another followed by `-`. Features\n     are named `\u003Carea>-\u003Cgoal>`, and `bin\u002Fverify uncovered \u003Carea>` finds an area's features\n     by that prefix.\n\n   Do not name features. Each recorder lists every behavior of its area from the source and\n   splits that list into features itself.\n2. Write each area's expectation list, as the Expectation lists section of the copied\n   `FULL.md` says.\n3. Write the first recipe yourself, for the simplest feature. Follow the Recipes section of\n   the copied `SKILL.md`, and name the recipe `\u003Carea>-\u003Cgoal>` after its area. That area's\n   recorder keeps it. Run `bin\u002Fverify \u003Cfeature>` until it passes. Every recorder copies\n   this recipe as its example, so make it clean. Then:\n   - Drive the main create path by hand once: create the same record twice, and read it as\n     a second tenant or user. Write what that shows about ids, uniqueness and shared data\n     into `PROJECT.md`'s Gotchas before any recorder starts, so no recorder hits the same\n     trap.\n   - Write the setup helpers several features need, such as signing in as each role,\n     creating an account with a role, provisioning a subscription or workspace, adding a\n     member, or reading the run's mail.\n   - Write the fixture helper for each row several features insert directly, such as a\n     user (the Data section's rule for such rows), before any recorder writes that insert\n     into a recipe.\n   - Call each helper once the way a recipe calls it, after deleting its cached state (such\n     as saved sign-ins), so its slow path runs too. A cache can hide a wrong argument until\n     the first fresh drive.\n   - Size each service's memory limit: about one and a half times what the service uses\n     after a busy run. A busy run is the example recipe's flow plus a few hundred sign-ins,\n     30 at a time. Read the use with `docker stats`. Never size the limit from an idle\n     stack.\n4. Run `bin\u002Fverify up --lanes 1`. A feature marked `# alone` waits until its copy is free\n   of other features, so on a single copy every other drive stops meanwhile. With the extra\n   copy, every drive runs its `# alone` features there instead. Then start recorders as the\n   Recorders section of the copied `FULL.md` says: one per area, every area at once,\n   heaviest first.\n5. Read only their result files. Add their traps to `PROJECT.md`'s Gotchas.\n\n## 5. Prove it\n\nRun `bin\u002Fverify down`. Then do steps 2 to 5 of Full in the copied `FULL.md`. Its first\n`verify all` starts a fresh environment on the production build, so every recipe runs once\nmore with every other feature beside it. Send a failing feature, an uncovered line or a\nnot-driven reason that does not hold back to the recorder that recorded its area, instead\nof starting a new one. In the final `verify all`, every feature runs on an environment\nwhere it already ran, which also proves each recipe repeats.\n\nThe runner starts up to as many features at once as the machine has cores, each only when\nthe machine-wide queue has room. Write a `jobs` file only when the project needs a lower\nlimit, such as a service with few connections. When `# alone` features remain, write into\nthe skill's `lanes` file the most extra copies a drive may start: about their total time\ndivided by the longest parallel feature.\n\nThen check the lifecycle once:\n\n- Run `bin\u002Fverify lint`. Fix every `# expects:` line it lists as citing code the checkouts\n  do not have: `bin\u002Fverify affected` can never select a feature through such a line.\n- Commit, change one line in a function that an `# expects:` line cites, and check that\n  `bin\u002Fverify affected --dry --base HEAD` lists that feature under \"Check the edited\n  code\". Without `--base HEAD` on this branch, every new recipe counts as changed. Undo\n  the change. In a companion, change a copy of the app checkout instead and point\n  `APP_\u003CNAME>` at it.\n- Check that `bin\u002Fverify down` leaves nothing of the run outside `.cache\u002F`: no process,\n  port, container, browser session or file.\n\n## 6. Instructions and hand-over\n\nWrite one `## Verification` section in the project's `AGENTS.md` from\n[`references\u002Fagents-verification.md`](references\u002Fagents-verification.md), with `\u003Capp>` and\nthe focused check commands filled in. In a companion repo it goes in the companion's\n`AGENTS.md`. Create the file when there is none.\n\n- Integrate an existing verification section instead of adding a second one. Rewrite a\n  section that points at a verify skill this run replaces.\n- If there is no `CLAUDE.md`, create one holding only `@AGENTS.md`. If one exists without\n  that import, put the same section there too.\n- Replace agent instructions for launching the app by hand with a pointer to the skill.\n  Leave the README's instructions for people.\n- Report an older verification system instead of deleting it.\n\nMerge `Bash(sudo:*)` into `permissions.deny` of `.claude\u002Fsettings.json`, keeping the rest.\nCommit following the repo's conventions. Report: the isolation level, how long recording and\n`bin\u002Fverify all` took, one line per feature (pass, fail with its kind, or blocked with what\nwas tried), and product defects found.\n",{"name":5,"metadata":24,"description":7,"disable-model-invocation":26},{"harness":25},"claude-code, codex, grok, cursor",true,"main","28de6d836930ed55586f8cac365c2a65381f432b","skills\u002Fcreate-project-verification-skill","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config","https:\u002F\u002Fgithub.com\u002Fthanostourik","https:\u002F\u002Fthanostourikas.gr","2026-11-15 02:45:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":26},[36,39,42],{"tool":37,"command":38},"npx","npx skills add thanostourik\u002Fagent-config --skill create-project-verification-skill",{"tool":40,"command":41},"bunx","bunx skills add thanostourik\u002Fagent-config --skill create-project-verification-skill",{"tool":43,"command":44},"pnpm","pnpm dlx skills add thanostourik\u002Fagent-config --skill create-project-verification-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002FSKILL.md",[47,53,57,61,65,69,73,77,83,87,91,95,99,103,107,111],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fagents-verification.md",1283,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fagents-verification.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fareas",9120,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fareas",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fclaude-stub.md",286,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fclaude-stub.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fdiscovery.md",3897,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fdiscovery.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ffull.md",5050,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Ffull.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fharvest",2956,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fharvest",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Flib.sh","SCRIPT","脚本",2252,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Flib.sh",{"path":84,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Flifecycle.md",7569,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Flifecycle.md",{"path":88,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fpw-close",1278,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fpw-close",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fpw.sh",4230,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fpw.sh",{"path":96,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Freach",21423,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Freach",{"path":100,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Frecorders.md",5870,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Frecorders.md",{"path":104,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fupgrade",8179,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fupgrade",{"path":108,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fverify",46053,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fverify",{"path":112,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fverify-skill.md",29181,"https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-project-verification-skill\u002Freferences\u002Fverify-skill.md",[116,123,130,137,144,151],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7C8QKD6FYHQHMV95PNHX8VZ","with-verification","Use when the user adds \"with verify\" or \"with verification\" to a task as an instruction to verify it with the project's verify skill. Not when verification is only the topic.","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fwith-verification\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7C8QFT8VQZ4YMEGEE2WEBJ6","triple-review","Use when the user asks for a triple review, or for three independent reviewers of a change.","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Ftriple-review\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7C8QE9S718F6ETYS7T93VV3","tourik","Use when the user asks for \"tourik mode\".","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Ftourik\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7C8QADG0HS20BPRMX0Y9CZ8","takeover","Use when the user asks to take over someone else's PR and get it ready for the user to merge.","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Ftakeover\u002FSKILL.md",[],[],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7C8Q6NBBZAPWY53TEP6VNY8","t3-fan-out","Use when the user wants several T3 threads or delegates started and coordinated, one per task.","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Ft3-fan-out\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7C8Q51MT7D68WHF8AY0FE5B","squash-merge-pr","Use only when the user explicitly invokes squash-merge-pr.","https:\u002F\u002Fgithub.com\u002Fthanostourik\u002Fagent-config\u002Fblob\u002Fmain\u002Fskills\u002Fsquash-merge-pr\u002FSKILL.md",[],[]]