wikipromptly8 shown

Coding

Prompts for software engineering.

Understand unfamiliar code before you have to change it

Get a layered explanation of pasted code: purpose, execution walkthrough, hidden gotchas, and a map of what is safe to change.

basic▲ 0

Generate a thorough unit test suite for one function

Produces a behavior-first test plan and then real unit tests covering happy paths, boundaries, error paths, and every visible branch.

basic▲ 0

Review a code change like a gatekeeping senior engineer

A code review that separates bugs, latent risks, and clarity problems, cites specific lines, and ends with a merge verdict.

basic▲ 0

Debug with an explicit hypothesis-and-evidence trail

Turns debugging into a checkable loop: facts, ranked hypotheses, and the single cheapest probe that separates them.

intermediate▲ 0

Plan and execute a behavior-preserving refactor

Refactors code through an explicit contract inventory, stepwise plan, and verification list — without changing observable behavior.

intermediate▲ 0

Compare architecture options and draft a decision record

A structured trade-off analysis against your stated priorities, the strongest case against each option, and a committable ADR.

intermediate▲ 0

Pin down legacy code with characterization tests before changing it

Builds a safety net around untested legacy code: dependency audit, minimal seams, behavior-pinning tests, and a go/no-go checklist.

advanced▲ 0

Run a differential diagnosis on an intermittent bug

For bugs that will not reproduce: candidate failure mechanisms, an instrumentation plan, and falsifiable predictions for the next occurrence.

advanced▲ 0
Crafted with precision by MnexWeb