Fill the Gaps in Your Logging
Coding
Audit the important paths and add useful, tested structured logs everywhere they are missing. Inspired by Forward Future's Loop Library.
Prompt
Step 1 — Map the important paths List the flows that are hardest to debug in production. Ask the AI where logging is missing or inconsistent along each. Step 2 — Add structured logs For the weakest path, add structured log lines that capture the context you would actually need at 2am. Step 3 — Test the logs Add tests that assert both the success and failure paths emit the expected log output. Step 4 — Repeat across paths Continue until every important path produces useful, tested logs. Stop when coverage is complete.
Use this prompt in AIniverse
Tap to copy, run it on ChatGPT / Claude / Gemini, save to your stack, or remix.
Open in AppMore Coding prompts
Independent Verifier Pass
When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implement...
API Contract Until Match
Loop until API responses match the OpenAPI or JSON Schema contract — catch drift between docs and implementation.
De-Sloppify Pass
After implementation, run a cleanup pass: remove debug code, tighten naming, delete dead branches, and align with pro...
Merge Conflict Resolver
Rebase or merge target branch, resolve conflicts file by file, and loop until the branch is current and tests pass.