issues SKILL.md skillA

issues from davidvornholt/standards is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add davidvornholt/standards/issues@git:20261107.b47c639

Pins git:20261107.b47c639 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
davidvornholt/standards
Path
.agents/skills/issues/SKILL.md
Versions recorded
4
Latest version
git:20261107.b47c639, committed Nov 7, 2026
First version recorded
Sep 3, 2026
Size
960 bytes
Repository stars
3
License
MIT

Use when opening an issue or changing its title or description.

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

# Issues

Whoever decides on an issue or picks it up, often an agent, reads it later without your context. Give it a plain-language title that names the problem or the desired outcome, and open the description with exactly these two paragraphs:

```md
**Problem.** The current behavior or missing ability, who or what it affects, and its concrete cost or risk.

**Outcome.** The observable result or decision that closes the issue.
```

The outcome says when the issue is done, not how. Name an implementation only when one is already decided, because whoever picks up the issue will treat a suggested approach as settled.

Put the support for the problem under `## Evidence`: observations, reproduction steps, measurements, code references, or sources, without restating the opening.

Add `## Decision` only when work can't start until someone makes a choice.

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_2uypwx4khulyesqr/1cb4ec0e6e7ec49530508b9108f1d4cae33fc8ba74fc6b090068924b5fd7a0e4.json

Then /plugin install issues@markdownregistry-2uypwx4khulyesqr in Claude Code. It installs git:20261107.b47c639, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add davidvornholt/standards/issues@sha256:1cb4ec0e6e7ec495

The line at the top of this page pins the label git:20261107.b47c639, 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_2uypwx4khulyesqr.svg)](https://markdownregistry.com/a/art_2uypwx4khulyesqr)

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 davidvornholt/standards/issues 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 issues from somewhere else? Ask it: where did my issues 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 4 versions of this file, between Sep 3, 2026 and Nov 7, 2026, about one every 22 days.

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

versioncommittedcommitsizeaudit
git:20261107.b47c639 latest2026-11-07 b47c639 960 BA view · diff
git:20261022.670c27d2026-10-22 670c27d 1,037 BA view · diff
git:20261022.9502c912026-10-22 9502c91 1,107 BA view · diff
git:20260903.a48472a2026-09-03 a48472a 806 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 (960 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

davidvornholt/standards · 3 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_2uypwx4khulyesqr
GET https://markdownregistry.com/api/v1/resolve?ref=davidvornholt/standards/issues
GET https://markdownregistry.com/api/v1/blob/1cb4ec0e6e7ec49530508b9108f1d4cae33fc8ba74fc6b090068924b5fd7a0e4

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 davidvornholt/standards

ci-pipelines SKILL.md skill
davidvornholt/standards · .agents/skills/ci-pipelines/SKILL.md · Use when changing continuous integration, GitHub Actions workflows, runners, caches, or deployment pipelines.
git:20261108.222c4d1 · audit A · 3 stars
database SKILL.md skill
davidvornholt/standards · .agents/skills/database/SKILL.md · Use when changing database schemas, migrations, database access, or database package structure.
git:20261107.b47c639 · audit A · 3 stars
declarative-infra SKILL.md skill
davidvornholt/standards · .agents/skills/declarative-infra/SKILL.md · Use when changing NixOS, OpenTofu, cloud resources, infrastructure secrets, deployments, or provider credentials, even…
git:20261107.b47c639 · audit A · 3 stars
frontend-design SKILL.md skill
davidvornholt/standards · .agents/skills/frontend-design/SKILL.md · Use when creating or visually styling a web interface.
git:20261107.b47c639 · audit A · 3 stars
nextjs SKILL.md skill
davidvornholt/standards · .agents/skills/nextjs/SKILL.md · Use when changing pages, layouts, Server Components, Route Handlers, Server Actions, caching, or rendering in a Next.js…
git:20261107.b47c639 · audit A · 3 stars
prs SKILL.md skill
davidvornholt/standards · .agents/skills/prs/SKILL.md · Use when opening or landing a pull request, or changing its title or description.
git:20261108.04648e3 · audit A · 3 stars
review-fix SKILL.md skill
davidvornholt/standards · .agents/skills/review-fix/SKILL.md · Use when asked to review a pull request and fix its findings in the same review loop.
git:20261108.3d6169f · audit A · 3 stars
review SKILL.md skill
davidvornholt/standards · .agents/skills/review/SKILL.md · Use when asked for a read-only review of code, documentation, configuration, or workflows.
git:20261107.e3d6154 · audit A · 3 stars
screenshots-in-prs SKILL.md skill
davidvornholt/standards · .agents/skills/screenshots-in-prs/SKILL.md · Use when opening or editing a pull request for a change to rendered UI.
git:20261107.b47c639 · audit A · 3 stars
secrets-and-config SKILL.md skill
davidvornholt/standards · .agents/skills/secrets-and-config/SKILL.md · Use when changing application configuration, environment variables, or generated development environments, or when…
git:20261108.7569d2b · audit A · 3 stars
standards-sync SKILL.md skill
davidvornholt/standards · .agents/skills/standards-sync/SKILL.md · Use when changing a file the standards sync manages (listed in `sync-standards.json`, such as `AGENTS.md`…
git:20261115.d0ef121 · audit A · 3 stars
ux-ui SKILL.md skill
davidvornholt/standards · .agents/skills/ux-ui/SKILL.md · Use when creating or changing a user-facing interface.
git:20261107.b47c639 · audit A · 3 stars

Every file in davidvornholt/standards

Other files named issues

issues SKILL.md skill
pedrohcgs/claude-code-my-workflow · .agents/skills/issues/SKILL.md · Keeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as…
git:20261106.a8c8716 · audit A · 1,718 stars
issues SKILL.md skill
pedrohcgs/claude-code-my-workflow · .claude/skills/issues/SKILL.md · Keeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as…
git:20261106.4145463 · audit A · 1,718 stars
issues SKILL.md skill
bjcoombs/ai-native-toolkit · skills/issues/SKILL.md · GitHub-issue marathon - triage open issues, then run agent-ready ones to merge with Agent Teams
git:20261008.d56b7ee · audit A · 32 stars
issues SKILL.md skill
vraj-ai/skills · standalone/issues/SKILL.md · Turn an agreed outcome into tracker issues with acceptance, dependencies, references, and verification. Keep planning…
v2.1.1 · audit A · 3 stars
issues SKILL.md skill
devskale/skale-skills · skills/issues/SKILL.md · Manage the cross-machine shared issue kanban (works/<project>/issues/). Create, triage, start, review, cancel, archive…
v1.5.1 · audit A · 2 stars

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

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.