On this page
Changes and verification
Review visible activity, resulting changes, and the checks that are relevant to your project.
RevampKey keeps work understandable by showing activity and making resulting changes available for review. Verification is part of that review, but what can be checked depends on the task and the tooling available in the project.
Read the visible activity
Follow the task and any delegated activity, including questions, permissions, interruptions, and the files that were read or changed.
Compare changes with the request
Look for scope creep, missing edge cases, and differences from an agreed plan or module breakdown.
Use relevant checks as evidence
Run or review tests and other checks when the project provides the needed tooling, then make your own decision from the files and results together.
Review activity and file changes
Inspect which files were read or changed and compare the result with the request. When a plan or module breakdown exists, compare implementation with those agreed goals. For grouped delegated activity, read Delegated work before treating a result as complete.
| Evidence | Question to ask | Useful next action |
|---|---|---|
| Visible activity | What happened and where did work stop? | Read the activity detail and any interruption message. |
| Changed files | Does the result stay within the requested scope? | Inspect the diff and nearby behavior. |
| Checks | What does the available tooling actually establish? | Use the result as evidence, not as a substitute for reading. |
Understand terminal and Git-related work
Depending on the task, RevampKey may perform relevant terminal work or show Git-related activity. Review command outcomes and the resulting file state in the context of your project. A task does not promise to create a commit for you; keep using the Git workflow that fits your project.
What if work fails or stops?
Read the visible failure or interruption details, inspect any changes already present, and decide whether to correct the request, retry a relevant check, or start a new task. If the result does not match the plan, revisit Specs, designs, and flows.
For context and connection issues, read Troubleshooting. For billing or plan questions, see Billing and usage.