Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Check for existing issues and PRs before creating new ones. Fires automatically when agent intends to file an issue, open a PR, or comment on a thread. Searc...
Check for existing issues and PRs before creating new ones. Fires automatically when agent intends to file an issue, open a PR, or comment on a thread. Searc...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Before creating a new issue or PR, search the target repo for existing threads that cover the same topic.
You are about to run gh issue create You are about to run gh pr create The user asks you to "file an issue", "open a PR", "report this bug", or "submit a fix" You are drafting a comment on an issue or PR you haven't read yet
Figure out which repo you're targeting. If you're inside a cloned repo, run: gh repo view --json nameWithOwner -q .nameWithOwner Summarize what your issue or PR is about in a few keywords.
Run both searches. Drop filler words (the, a, is, for, with, this, that, when, not, but, and, from) from your keywords. gh search issues --repo OWNER/REPO "KEYWORDS" --limit 5 --json number,title,state,comments gh search prs --repo OWNER/REPO "KEYWORDS" --limit 5 --json number,title,state,comments
Read the titles and comment counts. If any look related: Open the thread: gh issue view NUMBER --repo OWNER/REPO or gh pr view NUMBER Read enough to understand whether your topic is already covered Check if the thread is active, stale, or closed
SituationActionExisting open thread covers your exact topicComment there instead of creating a new oneExisting closed thread solved itDon't reopen โ link to it if relevantExisting thread is related but differentProceed with new issue/PR, reference the related threadNo matchesProceed normally
Show what you found before proceeding: Found existing threads that may cover this: #13738 โ WSL2 clipboard paste broken (16 comments, open) #14635 โ Paste not working in WSL (3 comments, open) Should I comment on an existing thread or create a new one?
Don't skip this check because you're confident your topic is new Don't create a new issue just because existing ones use slightly different wording Don't run expensive analysis โ two gh search calls is enough Don't block the user โ if they insist on creating a new thread after seeing duplicates, do it
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.