ds-pr-comment-proc

星标0

分支2

更新时间2026年6月18日 10:37

Fetch, inspect, reply to, resolve, and verify GitCode Pull Request review comments for yuanrong-datasystem or compatible GitCode repositories. Use when the user asks to pull PR comments, address review comments, reply under each review discussion, mark comments resolved, verify resolved state, or continue after PR review feedback.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

openeuler-mirror

openeuler-mirror/yuanrong-datasystem

打开 GitHub 仓库查看创作者相关仓库

下载

DS PR Comment Proc

Purpose

Use this skill after code fixes are ready or when a PR review needs to be processed. Always fetch comments before editing or replying, fix and verify code before resolving a discussion, and keep replies PR-safe.

Configuration

The script reads GitCode owner/repo/API settings from .skills/ds-pr-review/assets/default_config.toml when available. It reads tokens from GITCODE_TOKEN, GITCODE_ACCESS_TOKEN, GITCODE_TOEKEN, or ~/.local/gitcode_token.

If credentials are missing, tell the user:

Set GITCODE_TOKEN or GITCODE_ACCESS_TOKEN, or put the token in ~/.local/gitcode_token.
Do not paste the token into chat or commit it.

Workflow

Fetch unresolved comments:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py list --pr <PR_NUMBER> --unresolved

Fix the code locally and validate it. Do not resolve a discussion before the fix is implemented and verified.
Prepare one reply per review discussion. Replies should say what changed and what was verified, without private hosts, IPs, ports, usernames, local paths, remote log paths, tokens, AK/SK, or raw sensitive payloads.
Dry-run the plan:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py process --plan /tmp/pr-comments.json

Apply replies and resolution:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py process --plan /tmp/pr-comments.json --apply

Verify final state:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py verify --plan /tmp/pr-comments.json

Plan Format

Use comment_id from the UI or discussion_id from script output.

{
  "pr": 1048,
  "items": [
    {
      "comment_id": 173510908,
      "reply": "已修复：说明具体代码改动和验证命令。",
      "resolve": true
    }
  ]
}

Rules

Always reply under the corresponding discussion before marking it resolved unless the user explicitly asks to resolve only.
Use discussion_id for mutation. comment_id is accepted as convenience input and mapped by the script.
Re-fetch comments after mutation; do not rely on mutation responses alone.
If verification reports resolved=false or missing replies, run the specific reply/resolve command again and re-verify.
Keep PR replies sanitized and concise.

同仓库更多 Skills

同仓库

ds-pr-review

openeuler-mirror/yuanrong-datasystem

Use when reviewing yuanrong-datasystem code, tests, scripts, docs, diffs, commits, pull requests, PR descriptions, or design changes for correctness, design-contract compliance, internal/public API design quality, naming clarity, developer experience, abstraction boundaries, module locatability, production diagnosability, misuse prevention, ownership/lifecycle safety, hot-path performance, concurrency and C++ safety, persistence, recovery, public API/config/docs coverage, Bazel/CMake build support, sensitive-information exposure, testing, operability, risk-calibrated comment quality, context-update risk, and GitCode PR review-comment publishing.

2026-07-220

ds-trace-triage

openeuler-mirror/yuanrong-datasystem

Analyze DataSystem trace bundles for slow latency or errors. Use for gzip/tar trace packages, worker/client trace IDs, RPC deadline exceeded, rpc slow, client summary, RemotePull, Get/Set/Create/Publish, URMA_ELAPSED_*, worker/time/flow/breakdown aggregation, and CodeGraph-backed source mapping.

2026-07-220

ds-create-pr

openeuler-mirror/yuanrong-datasystem

Create GitCode Pull Requests for openeuler/yuanrong-datasystem or other GitCode repositories by calling the GitCode OpenAPI. Use when the user asks to create, submit, or open a PR for a pushed branch, especially after preparing docs or code commits that must target doc_pages, master, or another GitCode branch. For openeuler/yuanrong-datasystem, the PR body must follow .gitee/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.zh-cn.md.

2026-07-110

gitcode-ci-diagnose

openeuler-mirror/yuanrong-datasystem

Use when a gitcode.com PR's /retest finished and you need to know which checks failed and why. Given a PR number, fetches openeuler-ci-bot comments, parses the check result table, identifies FAILED checks, extracts console URL, fetches console output, and pinpoints failing test cases + actual error messages. Saves 10+ manual API/web fetches per diagnosis.

2026-07-100

ds-log-analysis

openeuler-mirror/yuanrong-datasystem

Analyze KVCache logs and generate interactive HTML reports with ECharts charts. Two scripts: access log analysis (QPS, latency, errors) and worker resource log analysis (memory, thread pools, cache hit rate, ETCD). Triggers: log analysis, access log, resource log, KVCache report, error analysis, QPS trend, latency P99, hit rate, thread pool, memory usage, worker resource, performance analysis, log report generation.

2026-06-250

ds-refresh-docs

openeuler-mirror/yuanrong-datasystem

Build and refresh the openYuanrong datasystem online Chinese documentation. Use when the user asks to update, refresh, or publish the online Chinese docs, especially when Codex needs to compile docs/source_zh_cn from the latest upstream master, sync build_zh_cn/html into doc_pages/docs/zh-cn/latest, create a documentation refresh commit, push a refresh branch to a fork, and automatically open a GitCode PR using $ds-create-pr.

2026-06-250

name	ds-pr-comment-proc
description	Fetch, inspect, reply to, resolve, and verify GitCode Pull Request review comments for yuanrong-datasystem or compatible GitCode repositories. Use when the user asks to pull PR comments, address review comments, reply under each review discussion, mark comments resolved, verify resolved state, or continue after PR review feedback.

DS PR Comment Proc

Purpose

Configuration

If credentials are missing, tell the user:

Set GITCODE_TOKEN or GITCODE_ACCESS_TOKEN, or put the token in ~/.local/gitcode_token.
Do not paste the token into chat or commit it.

Workflow

Fetch unresolved comments:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py list --pr <PR_NUMBER> --unresolved

Fix the code locally and validate it. Do not resolve a discussion before the fix is implemented and verified.
Prepare one reply per review discussion. Replies should say what changed and what was verified, without private hosts, IPs, ports, usernames, local paths, remote log paths, tokens, AK/SK, or raw sensitive payloads.
Dry-run the plan:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py process --plan /tmp/pr-comments.json

Apply replies and resolution:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py process --plan /tmp/pr-comments.json --apply

Verify final state:

python3 .skills/ds-pr-comment-proc/scripts/pr_comment_proc.py verify --plan /tmp/pr-comments.json

Plan Format

Use comment_id from the UI or discussion_id from script output.

{
  "pr": 1048,
  "items": [
    {
      "comment_id": 173510908,
      "reply": "已修复：说明具体代码改动和验证命令。",
      "resolve": true
    }
  ]
}

Rules

Always reply under the corresponding discussion before marking it resolved unless the user explicitly asks to resolve only.
Use discussion_id for mutation. comment_id is accepted as convenience input and mapped by the script.
Re-fetch comments after mutation; do not rely on mutation responses alone.
If verification reports resolved=false or missing replies, run the specific reply/resolve command again and re-verify.
Keep PR replies sanitized and concise.