openclaw
diff --git a/‎.agents/skills/openclaw-pr-maintainer/SKILL.md‎
Lines changed: 1 addition & 0 deletions b/‎.agents/skills/openclaw-pr-maintainer/SKILL.md‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.github/pr-assets/compaction-checkpoints/sessions-checkpoints-inline.png‎
-85.9 KB b/‎.github/pr-assets/compaction-checkpoints/sessions-checkpoints-inline.png‎
-85.9 KB
diff --git a/‎.github/pr-assets/compaction-checkpoints/sessions-overview-inline.png‎
-43.7 KB b/‎.github/pr-assets/compaction-checkpoints/sessions-overview-inline.png‎
-43.7 KB
diff --git a/‎.github/pr-assets/control-ui-chat-detail/context-collapsed-full-date.png‎
-37.9 KB b/‎.github/pr-assets/control-ui-chat-detail/context-collapsed-full-date.png‎
-37.9 KB
diff --git a/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions b/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions
@@ -68,6 +68,7 @@ gh search issues --repo openclaw/openclaw --match title,body --limit 50 \
 - Keep commit messages concise and action-oriented.
 - Group related changes; avoid bundling unrelated refactors.
 - Use `.github/pull_request_template.md` for PR submissions and `.github/ISSUE_TEMPLATE/` for issues.
+- Do not commit PR-only artifacts such as screenshots under `.github/pr-assets`; attach them to the PR/comment or use an external artifact store instead.
 
 ## Extra safety
 
 
@@ -60,6 +60,7 @@ Telegraph style. Root rules only. Read scoped `AGENTS.md` before subtree work.
 - PR shortlist: `gh pr list ...`; then `gh pr view <n> --json number,title,body,closingIssuesReferences,files,statusCheckRollup,reviewDecision`.
 - After landing PR: search duplicate open issues/PRs. Before closing: comment why + canonical link.
 - GH comments with markdown backticks, `$`, or shell snippets: avoid inline double-quoted `--body`; use single quotes or `--body-file`.
+- PR execution artifacts/screenshots: attach them to the PR, comment, or an external artifact store. Do not add `.github/pr-assets` or other PR-only assets to the repo.
 - PR review answer must explicitly cover: what bug/behavior we are trying to fix; PR/issue URL(s) and affected endpoint/surface; whether this is the best possible fix, with high-certainty evidence from code, tests, CI, and shipped/current behavior.
 - CI polling: exact SHA, needed fields only. Example: `gh api repos/<owner>/<repo>/actions/runs/<id> --jq '{status,conclusion,head_sha,updated_at,name,path}'`.
 - Post-land wait: minimal. Exact landed SHA only. If superseded on `main`, same-branch `cancel-in-progress` cancellations are expected; stop once local touched-surface proof exists. Never wait for newer unrelated `main` unless asked.