GET THE BUILD
[04]UNCENSORED CODER / OPERATING NOTES

TERMINAL AND SSH.
EVIDENCE FOR AI CODING.

A command has output. A process has a state. A changed file has a diff. Keep those signals close to the decision you are about to make.

LOCAL / REMOTECOMMAND REFERENCE / NOTHING RUNS HERE
$git status --short

Inspect the current working tree before deciding which files belong to your task.

CHECK THE TARGET

Confirm the directory first. Existing modifications may belong to someone else.

WHEN THE MACHINE IS REMOTE

VERIFY THE HOST.
THEN THE INTENTION.

01

CONFIRM

Know which server, user and working directory will receive the command.

02

BOUND

Start read-only. State explicitly when a task must not restart services or modify configuration.

03

RECOVER

A production change needs a backup, an exit condition and a way back.

These are examples, not a deployment plan. Use commands appropriate to your repository and environment.

THE PRACTICAL CONTEXT

Command output is evidence, not the entire conclusion

A command answers a specific question. A compact status view shows the working tree; a diff summary does not reveal every changed line. A project test script only checks what that script actually runs. Choose the command that provides evidence for the decision at hand.

When the target is remote, confirm the machine and directory again before acting. Keep inspection separate from restarts, installations or deployments. The command examples can be copied and adapted, but they are not executed by this website and do not replace a plan for your environment.

[NEXT]NO SINGLE MODEL OWNS YOUR PROCESS.

LET THE OUTPUT
SPEAK.

GET THE CODER