agentleFS
Sign inStart free
open-agent-poweropen-agent-power/open-knowledge-studio/.claude/skills/review-upstream-pr/SKILL.md

review-upstream-pr

Skill9 starsChanged 3 months agoMITView on GitHub

Independently review the remediation for upstream Open Knowledge Studio PR 4. Use after another agent implements the approved blocking fixes to inspect diffs, validate security and cross-platform behavior, run tests, and return a merge or rework verdict without editing code or writing to GitHub.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default setup output and failures never contain a fixture Base token.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review upstream PR 4 remediation

Act only as reviewer. Do not edit product code, commit, push, create a PR, resolve threads, or contact GitHub.

Review gates

  • .oks/candidates/, .oks/runs/, and .oks/locks/ are ignored without excluding tracked source files.
  • Feishu modules import without Lark installed. Runtime resolution honors LARK_CLI_EXE, Windows wrappers, and Unix lark-cli.
  • Default setup output and failures never contain a fixture Base token; only --show-credentials may display it.
  • Error text written back to Base has no Bearer/token value or user home path, and is truncated only after sanitization.
  • Raw documentation preserves Raw/not-knowledge, no-silent-loss, and provenance invariants; it maps v0.1 readers to v0.2 schemas without inventing a second v0.2 authority.

Evidence and verdict

Inspect the diff against the remediation base, run focused tests plus the full suite and git diff --check, then report each gate as pass/fail with command evidence. List non-blocking issues separately. End with exactly one verdict: ready_for_user_review or rework_required.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free