update-tests SKILL.md skillA

update-tests from alexkey/cookiecutter-uv-core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add alexkey/cookiecutter-uv-core/update-tests@git:20261114.d1b5269

Pins git:20261114.d1b5269 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
alexkey/cookiecutter-uv-core
Path
{{ cookiecutter.repo_name }}/.agents/skills/update-tests/SKILL.md
Versions recorded
3
Latest version
git:20261114.d1b5269, committed Nov 14, 2026
First version recorded
Nov 10, 2026
Size
25,754 bytes
Repository stars
6
License
BSD-3-Clause

Create new tests or update existing ones in the project, at any test level, without assuming a language, framework, or layout. Takes a mode and a required path that names where the tests live. Mode `create` writes tests at that path for the code or behavior named in the instructions. Mode `update` audits and refactors the tests found there to close coverage gaps, remove redundancy, strengthen weak assertions, and eliminate flakiness and nondeterminism. The skill learns the tooling…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Update Tests

Create and maintain automated tests that people can trust: each test fails when the
behavior it guards breaks, passes when it does not, runs quickly, and earns its place.
The skill has two modes, `create` and `update`. Both meet the same quality bar.

The skill carries no knowledge of particular languages, frameworks, or project layouts.
It works from two inputs. The first is the given `path`, the only place where it locates
and changes tests. The second is a profile of the surrounding project, built from
evidence before any planning.

## Agent compatibility

This skill uses the open Agent Skills format and runs unchanged in Claude Code and
OpenAI Codex. Codex reads the canonical copy in `.agents/skills/update-tests/`. Claude
Code reads `.claude/skills/update-tests`, a symlink to it. Edit only the canonical copy.

Every step relies only on capabilities both agents share: running shell commands and
searching, reading, and editing files. Paths such as `references/test-smells.md` are
relative to the directory containing this file. Use the extras that a host offers, but
do not depend on them. Such extras include structured questions, task lists, and a
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_nqbhymthneeg4jqh/4bf5ca31dc8ca313d61daf5c4a1cbc31b37ef8a110b837207d315d3efb8fe7df.json

Then /plugin install update-tests@markdownregistry-nqbhymthneeg4jqh in Claude Code. It installs git:20261114.d1b5269, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add alexkey/cookiecutter-uv-core/update-tests@sha256:4bf5ca31dc8ca313

The line at the top of this page pins the label git:20261114.d1b5269, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_nqbhymthneeg4jqh.svg)](https://markdownregistry.com/a/art_nqbhymthneeg4jqh)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in alexkey/cookiecutter-uv-core/update-tests since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of update-tests from somewhere else? Ask it: where did my update-tests come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Nov 10, 2026 and Nov 14, 2026, about one every 2 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261114.d1b5269 latest2026-11-14 d1b5269 25,754 BA view · diff
git:20261112.0e293142026-11-12 0e29314 25,612 BA view · diff
git:20261110.591d1842026-11-10 591d184 24,011 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (25754 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

alexkey/cookiecutter-uv-core · 6 stars · license BSD-3-Clause · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_nqbhymthneeg4jqh
GET https://markdownregistry.com/api/v1/resolve?ref=alexkey/cookiecutter-uv-core/update-tests
GET https://markdownregistry.com/api/v1/blob/4bf5ca31dc8ca313d61daf5c4a1cbc31b37ef8a110b837207d315d3efb8fe7df

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from alexkey/cookiecutter-uv-core

develop SKILL.md skill
alexkey/cookiecutter-uv-core · {{ cookiecutter.repo_name }}/.agents/skills/develop/SKILL.md · Plan, implement, and optionally test a substantial change in three stages, each opened only by the user's explicit…
git:20261114.5294817 · audit A · 6 stars
AGENTS.md@{{ cookiecutter.repo_name }} AGENTS.md file
alexkey/cookiecutter-uv-core · {{ cookiecutter.repo_name }}/AGENTS.md
git:20261116.44dd0a3 · audit A · 6 stars

Every file in alexkey/cookiecutter-uv-core

Browse by kind, by grade A, or by owner.