cglearn — Practice a better workflow

01 / PREDICT

A bug report offers a screenshot, a log, a configuration file and a proposed diagnosis. Which parts actually help explain the failure?

Your prediction

Write a brief prediction before opening the explanation.

02 / EXPLAIN

Read the lesson

Start with the question you need to answer

A context packet is a small set of evidence selected for a specific task. For a duplicate submission, the useful question is what allows a second request while the first is pending. A screenshot of a button may show its appearance but not the request sequence. The submit handler, observed steps and relevant test can help answer that question. State the purpose of each item; do not make the agent infer why an unrelated folder was attached.

Separate observations from interpretations

Record what happened, under which conditions, and what should have happened. Keep a suggested cause labeled as a hypothesis. If a customer says the database is broken, preserve the observed duplicate records without promoting that diagnosis into a requirement to replace storage. Include enough surrounding code to follow the behavior, with paths and the revision when available. Mark stale excerpts and missing sections so the agent can inspect their current versions.

Minimize exposure without removing the evidence

Replace sensitive values with synthetic examples that preserve the relevant shape. A request sequence can usually be explained without a session cookie or a customer record. If private code must be sent to an external provider, obtain the necessary consent before transmission. Omitting credentials does not make every remaining file public. Ask for additional context when a concrete uncertainty warrants it; neither the shortest packet nor the largest upload is automatically best.

Common mistake

Sending every available file, or withholding the reproducible failure while supplying only a confident diagnosis.

03 / DEMONSTRATE

Make the request actionable

A weak starting brief: The database must be broken. Here is every file and the production log. Rewrite the save flow.

Investigate duplicate form submissions. First inspect repository instructions and the current submit handler. Use the redacted reproduction steps and the pending-request test as evidence. Treat the database diagnosis as an unconfirmed hypothesis. Preserve normal success, failure and retry behavior. Request only the additional context needed to resolve a specific uncertainty, and do not transmit private material without authorization.

This example is an adaptable request, not evidence that a runtime action has executed.

04 / PRACTICE

Duplicate checkout requests

Simulated inventory:
A. Redacted steps: double-click Submit during a slow request; two records appear.
B. Current submit handler and pending-state test.
C. Production environment file containing credentials.
D. Screenshot of an unrelated dashboard.
E. Comment: the database must be broken; no investigation supplied.
Task: stop duplicate submissions while preserving retry after failure.

Simulated scenario · No repository access or command execution

Which starting context packet is strongest?A and E; instruct Codex to replace the database.A and B; label E as an unconfirmed hypothesis and omit C and D.Everything, because more context always improves correctness.D alone; visual evidence establishes request behavior.

Loading your saved lesson progress…