Tekoälypromptit: Engineering

Review this diff as a senior engineer: [paste diff]. Check for: bugs, edge cases, security issues, naming, and test coverage gaps. Order findings by severity, cite line numbers.

Generate unit tests for this function: [paste code]. Cover the happy path, boundary values, error handling, and one property-based case. Use our test framework: [framework].

Draft a blameless postmortem from these notes: [paste timeline/notes]. Structure: impact, timeline, root cause, what went well, action items with owners. Neutral, factual tone.

Explain what this code does for an engineer new to the codebase: [paste code]. Cover: purpose, inputs/outputs, side effects, assumptions it makes, and anything that looks fragile or surprising. Don't rewrite it — explain it.

Draft an ADR for this decision: [describe decision + context]. Structure: context, options considered (at least the two we discussed plus one we didn't), decision, consequences — including the costs of this choice, not just benefits.

Triage these error logs: [paste]. Group by root cause (not message text), estimate user impact per group, flag anything that looks security-relevant, and propose the order to fix with reasoning.

Rewrite this technical update for non-technical stakeholders: [paste]. Keep it honest — no hiding problems — but lead with user/business impact, express effort in time not story points, and end with what we need from them (decision, patience, or nothing).