mingyang1996

openclaw-gitcode-pr-monitor

Developmentv0.1.2
By mingyang1996Updated 2026-05-113 versions · latest released 2026-03-15@clawhub_mingyang1996/openclaw-gitcode-pr-monitor
Code ReviewScriptingGit

According to AlphaMoat, as of 2026-09, openclaw-gitcode-pr-monitor has 1,006 downloads and 0 stars — ranked #5,032 of 5,078 AI skills overall, and #574 of 577 in Development.

Installs
107
Downloads
1.0K
Stars
-
Overall Rank
#5,032
Top 100% overall · Top 100% in Development
PlatformInstallsDownloadsStarsComments
ClawHub ↗22876-2
SkillHub ↗1071.0K-—

Platforms count differently and update at different times.

What this skill does

The primary describes detecting new PRs, invoking OpenClaw to generate a Markdown review, posting it as a comment, and sending DingTalk or WeCom notifications. The workflow uses GitCode credentials and sends content to external systems. Before enabling it, use a least-privilege token, review notification targets and reports, and isolate untrusted PR content that may contain malicious changes or prompt injection. Do not auto-post comments or attachments without review.

Profile published 2026-10-29

What you can do with it

  • Summarize PR status in a specified repository
  • Draft a local review report without posting a comment
  • Review notification targets and GitCode token permissions

When to use it

  • When monitoring GitCode PRs and preparing review reports
  • When credentials and notification targets can be managed safely
  • When a human can review reports before comments or notifications are sent

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

Summarize PRs in this repository without posting a comment
Draft a review and flag content that needs human verification
Check notification targets and token permissions before enabling automation

Monthly Trend

Downloads1.0K
1686181.1K2026-03 · Downloads 2302026-05 · Downloads 5272026-06 · Downloads 6132026-07 · Downloads 7712026-08 · Downloads 8362026-09 · Downloads 1.0K26-0326-09
Stars-
0112026-03 · Stars -2026-05 · Stars -2026-06 · Stars -2026-07 · Stars -2026-08 · Stars -2026-09 · Stars -26-0326-09

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

MonthDownloadsMoMStars
2026-091.0K—-
2026-08836+8.4%-
2026-07771+25.8%-
2026-06613+16.3%-
2026-05527—-
2026-03230—-

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

1.9 KB · ClawHub v0.1.2
---
name: openclaw-gitcode-pr-monitor
description: Monitor GitCode PRs for one or more repos, auto-run AI review via OpenClaw Gateway, post PR comments, and send notifications (DingTalk + WeCom).
---

# openclaw-gitcode-pr-monitor

This skill packages a production-ready GitCode PR monitoring + auto-review pipeline.

## What it does
Show all (61 lines)

- Poll GitCode PR list for one or more repos (defaults use **anonymous placeholders**: `ExampleOrg/example_repo_1` + `ExampleOrg/example_repo_2`)
- When a new PR is detected:
  - send “review started” notification
  - run `openclaw agent` to generate a Markdown review report
  - post the report back to the PR as a comment
  - send “review finished” notification + attach the report

## Files

- `scripts/monitor-gitcode-pr.sh` — fetch latest PR, compare state, output `NEW_PR_DETECTED`
- `scripts/gitcode-pr-monitor-agent.sh` — orchestrator (multi-repo loop)
- `scripts/code-review-robust.sh` — run AI review (repo-aware, daily rotated session id)
- `scripts/submit-pr-comment.sh` — post PR comment (repo-aware)

## Quick start

1) Put your GitCode token at:

- `$HOME/.openclaw/workspace/data/gitcode-token.txt`

2) Configure notification targets

This packaged version defaults to DingTalk + WeCom, but you **must** set your own targets.

Recommended (env vars):

```bash
export TARGET_DINGTALK="<your-dingtalk-target>"
export TARGET_WECOM="user:<wecom-userid>"
```

3) Configure repos

Recommended (env vars):

```bash
export REPO_OWNER="<your-org>"
export REPOS_CSV="repo_a,repo_b"
```

4) Install cron

Example (every 5 minutes):

```cron
*/5 * * * * OPENCLAW_WORKSPACE="$HOME/.openclaw/workspace" REPO_OWNER="..." REPOS_CSV="..." TARGET_DINGTALK="..." TARGET_WECOM="..." $OPENCLAW_WORKSPACE/skills/openclaw-gitcode-pr-monitor/scripts/gitcode-pr-monitor-agent.sh >> $OPENCLAW_WORKSPACE/logs/cron-gitcode-pr.log 2>&1
```

See: `references/CONFIG.md`.

Popular in Development

Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.