How to Write a Pre-commit Hook Config from a Stack Brief

Pre-commit files invent rev hashes and mirror URLs. Repos allow list was two GitHub links. Pin nothing else.

The matching generator is the Pre-commit Hook Config from a Stack Brief (No Invented Hooks) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Hooks only with a Repo URL

Generate a pre-commit config from a stack brief. No invented hook repos, revs, or secrets. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Stack brief (languages, package managers): [Stack]
Hooks I allow by name: [Hooks]
Python/Node versions I lock (or UNKNOWN): [Versions]
Files or globs to exclude: [Exclude]
Words I must not use: [Banned]
What I must never invent: [Never]
Local hooks I may define (or NONE): [Local]
Output format: [Format]
Default stages I allow: [Stages]
Repo URL allow list for hooks: [Repos]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Versions UNKNOWN stays unknown

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: Stack, Hooks, Versions, Exclude, Local, Stages, Repos. Forbidden: hook repos not in Repos, invented revs.
2. Header comment stating Stack and Versions.
3. repos blocks only for Hooks that have a URL in Repos.
4. If a Hook has no Repo URL, mark gap instead of inventing.
5. Local hooks only if Local not NONE.
6. Exclude globs as given.
7. Refuse secrets in the file.
8. Compliance pass: cut Banned and Never. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Exclude globs as pasted

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• pre-commit config from Stack. Not GitHub Actions and not a vuln scan.
• Never invent hook repo URLs or revs.
• If Versions UNKNOWN, write unknown rather than picking 3.12.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

No secrets in the YAML

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (pre-commit hook config, stack brief pre-commit, no invented hook repos) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.