跳到正文
cccskills
免费在 GitHub 公开

PR Rescue

Use when reviewing, fixing, or verifying a pull request. Focus on correctness regressions, missing tests, permission mistakes, unsafe behavior, and minimal fixes.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

PR Rescue Skill

Use this skill when an agent must rescue a pull request.

The goal is not to produce a long review. The goal is to decide whether the PR is safe, find the most important problem if it is not, and identify the smallest fix and test.

Process

  1. Identify the changed files, touched public APIs, and affected workflows.
  2. Recall prior project memory before making claims.
  3. Look for correctness regressions first.
  4. Check permission, tenant isolation, auth, destructive operations, and empty input behavior.
  5. Verify that the PR has a targeted test for the changed behavior.
  6. Separate confirmed findings from guesses.
  7. Prefer one high-confidence finding over many speculative findings.
  8. Recommend the smallest patch that fixes the behavior.
  9. Name the exact test that should pass after the fix.

Review Checklist

For every changed workflow, ask:

  • What input used to work that might now fail?
  • What empty, missing, duplicate, or unauthorized input can reach this code?
  • Does this path write to graph, vector, relational, cache, or file storage?
  • Can a partial failure leave inconsistent state?
  • Are user, tenant, dataset, or permission checks preserved?
  • Does the test prove the changed behavior, or only the happy path?

Output Format

Return only actionable review or rescue output.

For each finding:

  • Severity: critical, high, medium, or low
  • Location: file path and line, symbol, endpoint, or workflow
  • Problem: what breaks and for whom
  • Evidence: why this is likely real
  • Fix: smallest practical change
  • Tests: exact test to add or run

If applying a patch, keep it minimal and explain what changed.

If no issues are found, say that directly and list the remaining test gaps or residual risk.

Self-Improvement Instructions

After each run, inspect the score and feedback.

If the run failed, update this skill with one concrete rule that would have prevented the failure.

Prefer targeted improvements:

  • "When graph writes include no relationships, verify empty edge batches are safe."
  • "When reviewing auth endpoints, require a signature verification check for decoded tokens."
  • "When a PR changes permissions, identify the user, tenant, dataset, and role boundary explicitly."

Avoid vague improvements:

  • "Be more careful."
  • "Think harder."
  • "Review everything better."

Keep the skill short enough that another agent can use it quickly.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use at a cognee hackathon. Watches the participant's experience with cognee throughout the session — errors, slowness, confusion, workarounds, and signs of frustration in how they work with you — and keeps one private feedback file they send to the cognee team at the end.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-hackathons112026年10月18日 更新

Use at the Mem Off hackathon. Keeps a running, evidence-backed report on how the participant's memory system performed for their coding agent during the day — what the harness measured, what cognee-report's scorecard says, what was recalled and whether it helped — in ./memoff-report.md and ./memoff-report.json. The report is submitted together with the action results; it never contains quotes, keys, data or names.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-hackathons112026年10月18日 更新

Build spend analytics and dashboards from Qdrant vector data. Covers bulk scroll extraction, aggregation patterns, vendor grouping, and Chart.js visualization. Use when building analytics features, aggregating procurement data, or creating dashboards.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-hackathons112026年10月18日 更新

Detect anomalies in procurement data using Qdrant vector operations. Covers centroid-based outlier detection, near-duplicate finding via batch recommend, amount z-score analysis, and vendor variance scoring. Use when building anomaly detection, fraud detection, or data quality features.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-hackathons112026年10月18日 更新

Semantic search over Qdrant Cloud collections using the Python client. Covers vector search, filtered search, prefetch+RRF fusion, group API, recommend API, discovery API, batch queries, scroll, and payload indexing. Use when building search features, adding new query types, or working with qdrant-client.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-hackathons112026年10月18日 更新

查看 topoteretes 的全部技能

报告此技能的问题