Work with files, terminal, and Review

Connect the change to its evidence#

Use files for source material, the terminal for command results, and Review for actual changes.

Prepare a small edit#

Choose a project, check its branch and existing changes, and attach a non-sensitive document. Version 1.1.22 includes project terminal reuse and split-screen Review, but terminal reuse does not reset its directory or environment.

Identify the project's documented check command. Use managed services for a persistent preview.

Edit and review one paragraph#

1. Attach the file and identify the paragraph.
2. Send the scoped request below.
3. Open Review and check the filename and each change.
4. Run the actual documentation check if one is applicable.

Clarify the setup paragraph in the attached document.
Keep the existing commands and technical meaning unchanged.
Edit only that paragraph; preserve unrelated modifications.
Show the diff and checks actually performed.
Do not commit or push.

Check files and commands#

Success means only the agreed content changed, existing work was preserved, and checks are recorded. In the terminal, inspect the directory, command, completion state, and relevant output.

“Edited locally,” “committed,” and “pushed” are different outcomes. A correct diff does not prove the latter two occurred.

Troubleshoot the working surfaces#

• Wrong file or directory: pause and confirm project and attachment.
• Output from earlier work: identify the current command before interpreting it.
• Unrelated changes in Review: retain existing work and narrow scope; do not revert everything.
• Check cannot run: record the missing dependency or permission and leave it unverified.

Expand the task#

Read permissions before broader edits. Use managed services for previews and projects and sessions for a separate task.