You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/openclaw-pr-maintainer/SKILL.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,21 @@ Use this skill for maintainer-facing GitHub workflow, not for ordinary code chan
35
35
- If the claim is unsubstantiated or likely wrong, request evidence or changes instead of merging.
36
36
- If the linked issue appears outdated or incorrect, correct triage first. Do not merge a speculative fix.
37
37
38
+
## Close low-signal manual PRs carefully
39
+
40
+
- Do not close for red CI alone. Require a clear low-signal category plus stale or failed validation.
41
+
- Good manual-close categories:
42
+
- blank or mostly untouched PR template with no concrete OpenClaw problem/fix
43
+
- random docs-only churn such as root README translations, generic wording tweaks, or community-plugin discoverability docs that should go through ClawHub
44
+
- test-only coverage without a linked bug, owner request, or behavior change
45
+
- refactor-only cleanup, variable renames, formatting, or generated/baseline churn without maintainer request
46
+
- third-party channel/provider/tool/skill/plugin work that belongs on ClawHub instead of core
47
+
- risky ops/infra drive-bys such as new external CI services, release workflows, host upgrade scripts, Docker base migrations, or apt retry/fix-missing tweaks without owner request and green validation
48
+
- dirty branches where a narrow stated change includes unrelated docs/generated/runtime/extension files
49
+
- repeated bot-review spam or copied bot output without author-owned fixes
50
+
- Keep or escalate plausible focused bug fixes, green PRs, active maintainer discussions, assigned work, recent author follow-up, and unique reproduction details.
51
+
- For third-party capabilities, prefer the `r: third-party-extension` auto-response label when it applies; it points contributors to publish on ClawHub.
52
+
38
53
## Handle GitHub text safely
39
54
40
55
- For issue comments and PR comments, use literal multiline strings or `-F - <<'EOF'` for real newlines. Never embed `\n`.
- Keep commit messages concise and action-oriented.
69
84
- Group related changes; avoid bundling unrelated refactors.
70
85
- Use `.github/pull_request_template.md` for PR submissions and `.github/ISSUE_TEMPLATE/` for issues.
86
+
- 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.
Copy file name to clipboardExpand all lines: .agents/skills/openclaw-qa-testing/SKILL.md
+73Lines changed: 73 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,79 @@ pnpm openclaw qa suite \
49
49
5. If the user wants to watch the live UI, find the current `openclaw-qa` listen port and report `http://127.0.0.1:<port>`.
50
50
6. If a scenario fails, fix the product or harness root cause, then rerun the full lane.
51
51
52
+
## OTEL smoke
53
+
54
+
For local QA-lab OpenTelemetry validation, use:
55
+
56
+
```bash
57
+
pnpm qa:otel:smoke
58
+
```
59
+
60
+
This starts a local OTLP/HTTP trace receiver, runs the `otel-trace-smoke`
61
+
scenario through qa-channel, decodes the emitted protobuf spans, and verifies
62
+
the exported trace names and privacy contract. It does not require Opik,
63
+
Langfuse, or external collector credentials.
64
+
65
+
## QA credentials and 1Password
66
+
67
+
- Use `op` only inside `tmux` for QA secret lookup in this repo.
68
+
- Quick auth check inside tmux:
69
+
70
+
```bash
71
+
op account list
72
+
```
73
+
74
+
- Direct Telegram npm live test secrets currently live in 1Password item:
75
+
- vault: `OpenClaw`
76
+
- item: `Telegram E2E`
77
+
- That item is the first place to look for:
78
+
-`OPENCLAW_QA_TELEGRAM_DRIVER_BOT_TOKEN`
79
+
-`OPENCLAW_QA_TELEGRAM_SUT_BOT_TOKEN`
80
+
-`OPENCLAW_QA_PROVIDER_MODE`
81
+
-`OPENCLAW_NPM_TELEGRAM_PACKAGE_SPEC`
82
+
- Convex QA secrets currently live in 1Password items:
83
+
- vault: `OpenClaw`
84
+
- item: `OPENCLAW_QA_CONVEX_SITE_URL`
85
+
- item: `OPENCLAW_QA_CONVEX_SECRET_MAINTAINER`
86
+
- item: `OPENCLAW_QA_CONVEX_SECRET_CI`
87
+
- Additional related notes/login items seen during QA credential work:
88
+
- vault: `Private`
89
+
- items: `OPENCLAW QA`, `Convex`, `Telegram`
90
+
- If a required value is missing from those notes:
91
+
- do not guess
92
+
- ask the maintainer/operator for the current value or the current 1Password item name
93
+
- for Telegram direct runs, `OPENCLAW_QA_TELEGRAM_GROUP_ID` may be stored separately from `Telegram E2E`
94
+
- for Convex runs, the leased Telegram credential should provide the Telegram group id and bot tokens together; do not require a separate `OPENCLAW_QA_TELEGRAM_GROUP_ID`
95
+
- for Convex runs, prefer `OpenClaw/OPENCLAW_QA_CONVEX_SITE_URL`; if that is stale or unclear, ask for the active pool URL before running
96
+
- Prefer direct Telegram envs for the npm Telegram Docker lane when available:
- do not assume `OPENCLAW_QA_PROVIDER_MODE` is consumed by that wrapper
114
+
- if a 1Password note only gives `OPENCLAW_QA_PROVIDER_MODE`, map it explicitly to `OPENCLAW_NPM_TELEGRAM_PROVIDER_MODE` before running the Docker lane
115
+
- Verified live shape:
116
+
- Convex mode can pass the real Docker lane without direct Telegram env vars
117
+
- leased Telegram payload includes the group id coupled to the driver/SUT tokens
118
+
- a real run of `pnpm test:docker:npm-telegram-live` passed with:
0 commit comments