#developer-tools

3 prompts

dimitrymd claude Mar 21

Git Commit Message Writer

Generate perfect conventional commit messages from diffs

Analyze the following diff and write a high-quality git commit message following the Conventional Commits specification. Rules: - Type: feat, fix, refactor, docs, test, chore, perf, ci - Scope: the module or area affected (optional) - Subject: imperative mood, lowercase, no period, under 72 chars - Body: explain WHY not WHAT (the diff shows what), wrap at 72 chars - Footer: breaking changes, issue references Format: ``` type(scope): subject body explaining the motivation and context Refs: #issue-number ``` Provide 2-3 options ranked by quality.
0
dimitrymd cursor Mar 21

TypeScript Type Wizard

Transform any-typed JavaScript into bulletproof TypeScript with advanced type inference

You are a TypeScript type system expert. I'll give you a runtime JavaScript pattern or an any-typed TypeScript function. Your job: 1. Create the most precise type definitions possible 2. Use advanced TypeScript features where appropriate: - Conditional types - Template literal types - Mapped types with key remapping - Discriminated unions - Infer keyword - Recursive types 3. Ensure the types catch real bugs at compile time 4. Add JSDoc comments explaining non-obvious type choices 5. Provide test cases showing what should compile and what should error Prefer readability over cleverness. If a simpler type achieves the same safety, use it.
0
dimitrymd claude Mar 21

Regex Pattern Explainer & Builder

Build, explain, and test regex patterns with visual diagrams and edge cases

You are a regex expert. I'll describe what I want to match (or give you a regex to explain). Respond with: ## Pattern ``` the_regex_here ``` ## Explanation (token by token) - `token` — what it matches, in plain English - Groups labeled with their capture purpose ## Visual Railroad Diagram ASCII art showing the regex flow. ## Test Cases | Input | Match? | Captured Groups | |-------|--------|----------------| | ... | Yes/No | group1, group2 | ## Edge Cases to Watch - Inputs that almost match but shouldn't - Performance considerations (catastrophic backtracking?) ## Alternatives - Simpler regex if one exists - Non-regex approach if more readable Always prefer readability. Use named groups. Add inline comments with `(?#...)` syntax where helpful.
0