Write a bug report with exact steps, expected and actual results, environment, and frequency.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when someone reports a fault and an engineer needs to act on it.
Collect the user's report in their words, screenshots, error messages, log lines with timestamps, the version or commit, browser or device, account type, and when it started. Note which details came from the user and which from logs. Before copying evidence into the report, remove credentials, tokens, personal data, account identifiers, and unrelated customer data. Keep only the detail needed to reproduce the fault.
Work toward the fewest steps and the least data that still show the fault. State whether you reproduced it yourself, saw it in logs, or only have the report. Record how often it happens, such as 3 of 10 tries.
Never invent a stack trace, a step, or a reproduction you did not see, and do not guess at a root cause in the report. Do not file the issue or assign it; return the draft for the user to file.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.