Decompose a spec, generate code and tests, run static analysis + sandbox, peer-review loop until green.

A tested regex from a plain-language description, with explanation and edge cases.

Developer-experience task automation: setup, dev, test, lint, build, deploy targets.

A robust automation script: argument parsing, dry-run, error handling, progress output.

Conventional-commit messages from a description of your change — subject plus body.

Paste any error — get the plain-language cause, likely fixes ranked, and how to prevent it.

Find the hot spots: complexity analysis, allocation churn, I/O patterns — optimized version included.

Refactoring pass on your code: smells found, then the improved version with rationale.

A risk-based test plan: scenarios by priority, edge cases, non-functional checks, exit criteria.

An incident runbook: symptoms → diagnosis → mitigation, escalation, and post-incident steps.

A senior-engineer review of your snippet: bugs, security, performance, style — with fixed code.

Reference documentation generated from your code: purpose, params, returns, errors, examples.

Diagnose a slow query: likely plan problems, rewritten query, and the indexes to add.

Turn a messy description into a triage-ready bug report with repro steps and severity.

A walkthrough of what the code does, how, and why — tuned to your experience level.

A system design proposal: components, data flow, tech choices with trade-offs, and risks.

A production-grade Dockerfile: multi-stage, small image, non-root, healthcheck — explained.

A complete GitHub README: badges plan, quickstart, usage, config table, contributing.

Keep-a-Changelog formatted release notes from your raw list — user-impact first.

A reviewer-friendly pull request description: context, changes, testing, risks, rollback.

Resource-oriented API design: endpoints, status codes, pagination, errors, versioning.

An OWASP-minded pass over your code: injection, authz, secrets, validation — with fixes.

INVEST-quality user stories with acceptance criteria and edge-case scenarios.

Great names for functions, classes, variables or modules — with the reasoning.