Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Pull Request
Create high-quality pull requests with pre-submission validation, maintainer-friendly formatting, and automated quality checks.
skill openclawclawhub Free
Create high-quality pull requests with pre-submission validation, maintainer-friendly formatting, and automated quality checks.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, checklist.md, red-flags.md, repo-context.md, templates.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
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.
Upgrade existing
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.1
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
When to Use
Before creating or suggesting a pull request to ANY repository. Acts as a quality filter to prevent wasting maintainer time and embarrassing the contributor.
Quick Reference
DomainFilePre-submission checklistchecklist.mdRed flags to avoidred-flags.mdRepository context gatheringrepo-context.mdPR description templatestemplates.md
Critical Rules
Read CONTRIBUTING.md first โ Adapt to project's workflow, not a fixed pattern Issue policy depends on scope โ Small fixes may PR directly; features need discussion first Disclose AI involvement โ Mark AI-assisted PRs in title/description Run checks if possible โ If you can't run tests, say so explicitly Match existing style โ Check for .editorconfig, prettier, eslint configs Small and focused โ One logical change per PR No secrets ever โ Use <PLACEHOLDER> syntax
Issue Policy (Contextual)
NOT all projects require issues first. Check CONTRIBUTING.md, then: Change TypeDefault ActionTypo, small bug fixPR directly (unless CONTRIBUTING.md says otherwise)New featureOpen Discussion/Issue first, wait for approvalArchitecture changeRFC or Discussion requiredWhen in doubtAsk in issue before coding
AI-Assisted PRs
If this PR was created with AI assistance: Mark it โ Add [AI-assisted] to PR title or note in description Testing level โ State: untested / lightly tested / fully tested Include context โ Prompts or session logs if available and helpful Confirm understanding โ "I have reviewed this code and understand what it does" Human accountable โ Link to the human directing the contribution
Rate Limiting (Avoid Spam)
MAX 1 open PR per repo at a time Wait 24h between PRs to same repo If 2 PRs rejected consecutively โ STOP and escalate to human Check repo's PR velocity first (don't flood low-activity projects)
Abandonment Prevention
MUST respond to review feedback within 48h If unable to address feedback, close with: "I cannot continue; @human please take over or close" Never leave PRs to rot
Scope Boundaries โ STOP and Discuss First If:
Change touches >5 files OR >200 lines Change modifies public API Change involves security, auth, or crypto Change is in governance, licensing, or CoC Maintainer requested discussion in issue You're unsure if this aligns with project philosophy
Human Escalation Required
Escalate to human when: Reviewer asks clarifying questions about design intent CI fails in non-obvious way Any pushback beyond "fix this typo" Reviewer seems confused or frustrated You can't run the test suite locally
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs
- SKILL.md
- checklist.md
- red-flags.md
- repo-context.md
- templates.md