Imported from jclark/satpulse (
AGENTS.md). Install upstream withnpx skills add jclark/satpulse. Copyright stays with the author.
Agent instructions
Proactive sandbox elevation
This workspace uses automatic approval for elevation. Request elevated permissions on the first attempt whenever a command is expected or reasonably likely to need resources outside the workspace sandbox. Do not run it sandboxed first merely to see whether it fails.
Always request elevation for:
ghcommands and network-facing Git commands- Git commands that modify branches, refs, the index, or commits
- Go builds, tests, generation, and project build scripts
- commands that use normal user, module, build, or tool caches
- authentication, downloads, network access, sockets, shared memory, or hardware access
Run the normal command unchanged with elevation. Do not redirect caches to /tmp, replace credentials, disable functionality, or otherwise create a sandbox-specific workaround.
Read-only commands confined to the workspace, such as rg, file inspection, git diff, git status, and git log, do not normally need elevation. When uncertain whether a required command needs outside access, prefer requesting elevation immediately.
Commit messages
Use judgment. For substantive non-merge changes, a one-line commit message is not enough: use a concise subject followed by a body that explains the problem, the behavior change, and any important implementation details. Routine merge commits may keep Git's generated one-line message, and trivial mechanical changes do not need a padded body.
Pull requests
When asked to create a pull request, create it ready for review. Do not create a draft unless the user explicitly requests one.
