Productivity tools for developers

Diagnoses a bug from a pasted error and the code around it, ranking likely causes and giving one check for each before any fix.

Writes reference documentation for one API endpoint from its handler code, with parameters, responses and an example request.

Drafts a CI pipeline config with build, test and lint stages for your stack, using secret placeholders and a comment on each stage.

Drafts a code formatter config file that keeps your style choices, with a comment on each added setting and the commands to run it.

Drafts a dev container configuration for your stack with editor extensions, ports and setup commands, each choice explained in one line.

Drafts a short project rules file that steers AI code completion toward my conventions, using the code samples I paste.

Drafts a config file for my terminal emulator with font, colors, scrollback and key bindings, and flags every option I should check.

Explains each warning in pasted linter output in plain words and shows the smallest fix, marking which ones are safe to ignore.

Reads pasted profiler output, names the likely bottleneck and proposes three experiments to confirm it, ranked by effort.

Finds the slowest steps in a pasted build log or timing output and suggests the three changes with the best payoff, safest first.

Finds the syntax and structure errors in a pasted JSON or YAML file, returns the corrected file and lists each change you should review.

Plans which events, fields and levels a service should log so problems can be traced, without logging personal data or secrets.

Reviews a pasted diff the way a careful colleague would and ranks at most eight findings from blocking to nitpick, each with a suggested fix.

Reviews a Dockerfile for image size, build speed and security habits, then returns one improved version with each change explained.

Reviews a SQL query for wrong results and slow spots, then suggests one rewrite with the reasoning and how to test it safely.

Reviews a pasted infrastructure as code plan for destroys, replacements and risky changes, and gives a go or no-go with the reasons.

Plans how to connect a database client to a development or production database with least privilege and no secrets in files.

Finds the commands I repeat most in a pasted shell history and suggests at most ten aliases or functions, each with a safety note.

Ranks static analysis findings by real risk, separates likely false positives, and names the three to fix first with a reason each.

Turns a task you do by clicking in a cloud console into a CLI command with each flag explained, a dry run first and any destructive step flagged.

Turns a rough coding task into one precise prompt for an AI coding assistant, with constraints, the files involved and a way to check the result.

Turns your description of a system into a diagram written as text, plus a list of the assumptions made so you can correct them.

Finds the repeated patterns in code you paste and turns the three most useful ones into snippets with a trigger word and tab stops.

Writes one regular expression for your examples of what to match and not match, explains each part, and lists the cases it still gets wrong.

Writes a list of API test cases for one endpoint, covering happy path, bad input, auth and limits, ready to turn into requests.

Writes unit tests for one function in my testing framework, covering normal, edge and failure cases, after reading the code.