Amir Publish

• amirs-m3-max
• agents@amirs-mac-studio
• amir-m5
• home
• claw

Treat agents@amirs-mac-studio as the host amirs-mac-studio when deciding whether to skip the current machine.

Workflow

1. Resolve the git repo root, current branch, current commit, and same absolute directory path to use on remotes.
2. Identify the current machine with hostname -s or the closest available hostname command.
3. Inspect git status --short. Default to committing the full tracked-file diff across the repo, including tracked changes you do not recognize. Unfamiliar tracked changes are not a blocker by themselves.
4. Stage tracked modifications and deletions with git add -u. Also stage untracked files that are clearly part of the current repo work; ask only for ambiguous untracked files or concrete safety issues such as secrets.
5. If there are changes to commit, create one concise commit. If there is nothing to commit, say so and continue.
6. Push the current branch to its upstream. If no upstream exists, push with git push -u origin <branch>.
7. Run the local install command from the repo root:

make install

8. For each non-skipped SSH target, run the remote sync from the same absolute directory:

cd <same-dir> &&
git fetch origin &&
(git checkout <branch> || git checkout -t origin/<branch>) &&
git pull --ff-only &&
make install

9. If one remote fails, continue to the remaining hosts unless the failure means the pushed branch or local install is invalid. Keep the failed host and command visible in the final summary.

Output

Keep the final response short:

• local branch and commit pushed
• local install result
• each remote host result
• any skipped host
• any failed host and the exact next repair step