clawdtributor

Automate triage and review of OpenClaw pull requests and issues.

18|1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/vignesh2027/Vilvona-AI --skill clawdtributor-vignesh2027
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clawdtributor
Source: https://github.com/vignesh2027/Vilvona-AI/tree/main/.agents/skills/clawdtributor
Command: npx skills add https://github.com/vignesh2027/Vilvona-AI --skill clawdtributor-vignesh2027

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, openclaw, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Clawdtributor Skill simplifies and automates the process of triaging, reviewing, and managing OpenClaw pull requests and issues.

Core Features & Use Cases

  • PR/Issue Triage: Discovers and rechecks PRs/Issues for live GitHub status.
  • Deep Review: Provides in-depth analysis and review for PRs/Issues.
  • Topic Grouping: Groups related items based on labels and content.
  • Summaries: Generates compact summaries with risk markers.
  • Use Case: A maintainer uses Clawdtributor to quickly assess the status and importance of open PRs and issues, streamlining the review process.

Quick Start

Start triage by using the clawdtributor check command.

Frequently Asked Questions about clawdtributor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR triage and issue management?

Deep review for GitHub pull requests performs in-depth code analysis and groups related issues or PRs based on content and labels, providing maintainers with a comprehensive assessment of open items.

Do I need GitHub API access to run OpenClaw PR reviews?

Yes, you need GitHub API access to run OpenClaw PR reviews, as the skill relies on live GitHub status checks and OpenClaw tooling integration to discover, triage, and review pull requests and issues.

What is the best way to group related GitHub issues and pull requests?

The best way to group related GitHub issues and pull requests is to use topic grouping, which clusters items based on their labels and content to streamline the triage and review process.

Can I use this to summarize open pull requests with risk markers?

Limitations of automated code review include the need for OpenClaw tooling integration and GitHub API access; without these dependencies, the triage and deep review processes cannot function.