Adapt agent guidance and supporting docs for BeatGlow
This commit is contained in:
5 files changed
+154
-1
No files matched your search
@@ -0,0 +1,20 @@
|
||||
# Operational guidance
|
||||
|
||||
- Follow the user's task and established preferences. Continue authorized work
|
||||
without repeatedly asking for confirmation; clarify genuinely missing decisions.
|
||||
- Inspect the code, branch, diff and relevant documentation before making changes.
|
||||
Verify external protocol behavior against upstream documentation when needed.
|
||||
- Keep changes within scope and preserve unrelated work. Explain a necessary
|
||||
scope change instead of silently bundling cleanup or dependency updates.
|
||||
- Communicate directly and briefly. Explain findings, behavior changes and remaining
|
||||
uncertainty; avoid flattery and unsupported claims.
|
||||
- Review the surrounding component after editing, including configuration,
|
||||
registration, lifecycle and callers affected by an interface change.
|
||||
- Test the behavior that changed. State which tests ran, which checks only
|
||||
compiled, and what requires Linux, hardware, network access or authentication.
|
||||
- Describe recoverable device/server failures realistically. Do not label an issue
|
||||
critical without evidence or claim a fix is verified on hardware without testing it.
|
||||
- Finish with concise results, links to changed files or the PR, and material
|
||||
limitations. Never report a PR created when only its branch was pushed.
|
||||
|
||||
Adapted from [Flow's operational guide](https://github.com/onflow/flow-go/blob/master/docs/agents/OperationalDoctrine.md).
|
||||
Reference in new issue
Block a user