agentleFS
mikhailkogan17mikhailkogan17/cycler/skills/workflow-review/SKILL.md

workflow-review

Skill0 starsChanged 18 days agoMITView on GitHub

Independently review an existing GitHub PR with configurable Claude, Codex or DeepSeek reviewers; publish line comments and verify implementer replies. Works standalone without Linear or an implementation run.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Independent GitHub review

Resolve cycler's installation root from CYCLER_ROOT, CLAUDE_PLUGIN_ROOT, or this skill's path (../..). Do not assume a Claude Workflow tool or Linear connection exists.

Given a PR URL or number, run:

node "$CYCLER_ROOT/harness/review.mjs" --cwd "$PWD" --pr '<PR>' --publish

This starts independent sessions for bugs, contract/scope and regression coverage. Configure review.runtime, review.model, or review.lenses in cycler's YAML for cross-model review. The harness fetches a detached snapshot of the PR head, verifies blocking findings against actual code, checks inline locations, and publishes a GitHub COMMENT review. This works when the authenticated account also authored the PR. The body says whether changes are required; it does not forge a GitHub APPROVED state.

Publication is part of this workflow. An empty review means all reviewers ran and found no blocking issues. A missing reviewer, stale head, invalid location or GitHub error is a failure, not approval. Report it and stop. Never substitute your own review for a failed independent lens. Without --publish, the helper returns a local report for an explicitly requested draft review.

For a requested fix, use the existing PR branch, fix verified findings, run the repo gate, commit and push. Read each returned thread; write a JSON array of {id, body} with a concrete explanation of the fix and test, or evidence for disagreement. Publish replies in those threads:

node "$CYCLER_ROOT/harness/review.mjs" --cwd "$PWD" --pr '<PR>' --replies /path/to/replies.json --commit '<full pushed SHA>'

Then run the review again against the new head. Never merge, resolve threads on the author's behalf, or claim a fix without inspecting it. Link the PR and mention any failed publication.

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.