poe-code 3.0.140 → 3.0.142
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -13,8 +13,11 @@ Read {{url}} and leave a visible GitHub response.
|
|
|
13
13
|
- If the issue needs code changes, implement them, open or update a PR, and comment with the result.
|
|
14
14
|
- If you cannot complete the request, comment with the blocker and the next concrete step.
|
|
15
15
|
|
|
16
|
-
Make the visible response clean and easy to scan:
|
|
17
|
-
|
|
18
16
|
- Start with a direct answer or decision.
|
|
19
17
|
- Keep it concise.
|
|
20
18
|
- Use short Markdown sections only when they improve clarity.
|
|
19
|
+
|
|
20
|
+
Before answering:
|
|
21
|
+
|
|
22
|
+
- Inspect the checked-out repository
|
|
23
|
+
- Verify every claim against the repo before you post it.
|
|
@@ -1,4 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
label: "Scheduled: Update Documentation"
|
|
3
3
|
---
|
|
4
|
-
Review
|
|
4
|
+
Review all commits that landed during the last 24 hours and update the documentation to reflect the full day's changes.
|
|
5
|
+
|
|
6
|
+
Use the branch `agent/update-documentation` for this automation.
|
|
7
|
+
If there is already an open, unmerged PR for that branch, update that existing PR with the new documentation changes instead of opening a new PR.
|
|
8
|
+
If the documentation is already correct, leave the repository unchanged and do not open or update a PR.
|