issue-prioritizer
Prioritize GitHub issues by ROI, solution sanity, and architectural impact. Use when triaging or ranking issues to identify quick wins, over-engineered proposals, and actionable bugs. Don't use when managing forks (use fork-manager) or general GitHub queries (use github). Read-only — never modifies repositories.
Why use this skill?
Analyze and prioritize GitHub issues using OpenClaw's issue-prioritizer. Identify quick wins, actionable bugs, and architectural impacts efficiently.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/glucksberg/issue-prioritizerWhat This Skill Does
The issue-prioritizer is a specialized analytical tool designed to help developers, maintainers, and project managers organize GitHub issue backlogs. It processes open issues in a repository, analyzing them based on Return on Investment (ROI), architectural impact, and overall solution sanity. Unlike standard listing tools, it applies a scoring logic to identify 'quick wins' versus over-engineered proposals, ensuring that development resources are focused on the most impactful tasks. This skill is strictly read-only, ensuring that it provides deep insights without altering the state of your repository.
Installation
To install this skill, use the following command in your terminal:
clawhub install openclaw/skills/skills/glucksberg/issue-prioritizer
Ensure that you have the GitHub CLI (gh) installed and authenticated on your local machine by running gh auth login before attempting to use the skill, as it relies on the gh CLI to securely fetch repository metadata.
Use Cases
This skill is perfect for:
- Triage Sessions: Quickly filtering through hundreds of open issues to find high-impact bugs or requested features.
- Contributor Onboarding: Identifying 'good first issue' candidates by filtering for low-complexity, high-value tasks.
- Architectural Health Checks: Flagging proposals that show signs of over-engineering or lack of alignment with existing project architecture.
- Sprint Planning: Aggregating issues based on specific labels or topics to streamline roadmap development.
Example Prompts
- "Prioritize the top 20 open issues in openclaw/skills based on ROI and highlight any quick wins for new contributors."
- "Search for issues labeled 'bug' in my project repo and rank them by architectural impact to help me decide what to patch first."
- "Find open issues about 'authentication' in the repository and list the most actionable ones."
Tips & Limitations
- Authentication: Always verify your
ghcredentials if the skill fails to fetch data. - Limits: If you are working on a massive repository, start with a smaller
--limitto avoid hitting GitHub API rate limits. - Search Nuance: When using
--topicor--search, leverage standard GitHub search syntax (e.g.,comments:>5) for more refined results. - Scope: This tool does not modify issues. If you need to manage forks or perform complex PR reviews, use the corresponding
fork-managerorpr-reviewskills instead.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-glucksberg-issue-prioritizer": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api, network-access
Related Skills
fork-manager
Manage forks with open PRs - sync upstream, rebase branches, track PR status, and maintain production branches with pending contributions. Supports automatic conflict resolution via --auto-resolve flag (spawns AI subagents to resolve rebase conflicts). Use when syncing forks, rebasing PR branches, building production branches that combine all open PRs, reviewing closed/rejected PRs, or managing local patches kept outside upstream. Requires Git and GitHub CLI (gh).
pr-ship
Pre-ship risk report for OpenClaw PRs. Dynamically explores the codebase to assess module risk, blast radius, and version-specific gotchas. Scores each finding by severity (🟢/🟡/🔴). Updated frequently with the latest OpenClaw version context — run `clawhub update pr-ship` regularly to stay current.
cross-ref
Cross-reference GitHub PRs and issues to find duplicates and missing links. Spawns parallel Sonnet subagents to semantically analyze the last N PRs and issues, finding PRs that solve the same problem (duplicates) and issues resolved by open PRs but not yet linked. Groups findings into thematic clusters, scores them by actionability, and offers rate-limited commenting or bulk actions (close, label). Use this skill when the user wants to find duplicate PRs, link issues to PRs, clean up a repo's cross-references, or audit PR/issue relationships. Also useful when the user says things like "find related PRs", "which PRs fix this issue", "are there duplicate PRs", "link issues and PRs", or "audit cross-references".
anti-pattern-czar
Detect and fix TypeScript error handling anti-patterns with state persistence and approval workflows. Use when scanning a codebase for silent error failures, empty catches, promise swallowing, or unlogged errors. Supports five modes — scan (detect all issues), review (interactive fix session), auto (batch fix with guardrails), resume (continue from last session), report (show progress). Triggers on phrases like 'scan for anti-patterns', 'fix error handling', 'find empty catches', 'anti-pattern czar', or 'check error handling'.
pr-review
Find and fix code issues before publishing a PR. Single-pass review with auto-fix. Use when reviewing code changes before submission or auditing existing code for bugs/security. Don't use when running a coding agent to write code (use coding-agent) or checking GitHub CI status (use github).