Best PromptsREADME From Your Code
Generate a README grounded in what the code actually does: verified commands, honest feature list, and no hallucinated flags.
Write a README for this project.
Audience: [WHO LANDS HERE: e.g. "developers evaluating whether to use this library" / "new team members" / "users installing the CLI"]
Project code (or explore the repo if you're an agent):
"""
[PASTE package.json/pyproject.toml, entry points, main modules, CLI/arg definitions]
"""
Rules before structure: every command, flag, config option, and code example in the README must come from the actual code provided. Check the scripts, arg parsers, and exports. If you can't verify a detail from the code, write [VERIFY: detail] instead of a plausible guess. A README with a wrong install command is worse than no README.
Structure:
1. **What it is**: one sentence: what it does and for whom. Then 2-3 sentences on when you'd use it, and when you wouldn't (name the alternative for that case).
2. **Quickstart**: the shortest real path from zero to seeing it work: install command, minimal example with its actual expected output. Pulled from the real entry points, runnable as written.
3. **Usage**: the 3-5 most important operations, each with a short example. Document the WHY where it's not obvious (a note on when to reach for each option), not a restatement of parameter names.
4. **Configuration**: actual options from the code, as a table: option | default | what it controls. Only options that exist.
5. **Development**: how to run tests and contribute, from the real scripts.
Style: no marketing adjectives ("blazingly fast", "powerful"), no badges wall, no empty sections ("Contributing: TBD" gets cut). Match the codebase's terminology exactly: don't rename concepts in prose.More coding prompts
Write the commit message for this change. Diff: """ [PASTE THE STAGED DIFF] """ Why I made this change: [THE REASON, THE TICKET, THE BUG REPORT, or "you infer it"] Convention: [Conventional Commits / this repo's existing style, pasted below / plain] Recent commits from this repo, to match style: """ [PASTE 5-10 RECENT COMMIT SUBJECT LIN
Commit Message
Write a commit message that explains why the change was made, in Conventional Commits format, split into separate commits when needed.
Codingbeginner
Help me recover from a git mistake without making it worse. What I was trying to do: [THE GOAL] What I ran: [THE EXACT COMMANDS, IN ORDER] What happened instead: [THE OUTPUT OR THE STATE NOW] Has this been pushed or shared: [YES/NO, and to which branch and whether anyone else has pulled] Uncommitted work I cannot lose: [WHAT AND WHERE, o
Undo a Git Mistake
Recover from a bad commit, force push, wrong branch, or lost work with a reversible plan and the exact commands, explained before you run them.
Codingintermediate
Handler code, routes, and models: """ [PASTE THE ROUTE DEFINITIONS, HANDLERS, REQUEST AND RESPONSE TYPES, VALIDATION SCHEMAS, AND MIDDLEWARE] """ Generate an OpenAPI 3.1 specification from the code above. API name, version, and base URL: [DETAILS] Auth scheme: [BEARER JWT / API KEY / OAUTH / SESSION COOKIE, and where it is enforced] Con
OpenAPI Spec From Code
Generate an accurate OpenAPI 3.1 spec from handler code, including error responses and auth, with gaps flagged instead of invented.
Codingintermediate