Pull Request

What This Skill Does

The Pull Request skill acts as an intelligent quality gate and administrative assistant for open-source and professional software contribution. It is designed to bridge the gap between AI-generated code and repository-level standards. This skill enforces rigorous pre-submission checks, ensures adherence to project-specific contribution guidelines, and manages the lifecycle of a PR to ensure it is maintainer-friendly and professional. It handles everything from file-specific linting checks to ensuring disclosure of AI-assistance, helping users navigate the social and technical complexities of collaborative development.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/pull-request Ensure you have the necessary repository permissions and local environment access configured before execution.

Use Cases

• Automated Quality Filtering: Validates code against project-specific CONTRIBUTING.md standards before any submission.
• PR Lifecycle Management: Automatically tracks response times and ensures you follow up on reviewer feedback within the mandatory 48-hour window.
• Compliance & Transparency: Handles the mandatory disclosure of AI-assisted code, ensuring the user and the assistant remain accountable to project maintainers.
• Safety-First Contributions: Identifies high-risk changes (e.g., security, crypto, or major API shifts) that require human discussion before a PR is opened.

Example Prompts

1. "OpenClaw, I have finished refactoring the utility class. Run the pre-submission checklist, check for existing PR guidelines in this repo, and draft a PR description highlighting the performance gains."
2. "I need to submit a bug fix for an issue in [repo_url]. Can you help me review the CONTRIBUTING.md file and verify if I should open an issue first or if I can go straight to a pull request?"
3. "Review my current PR draft. Does it meet the criteria for an AI-assisted submission, and have I accurately documented the testing level based on our session logs?"

Tips & Limitations

• Respect the Velocity: Always check the repository's PR frequency. Don't spam low-activity projects.
• Human-in-the-Loop: This skill is an assistant, not a replacement for judgment. If a PR involves core security architecture, consult with a human maintainer immediately.
• Rate Limiting: Adhere strictly to the one-PR-at-a-time rule to avoid being flagged as a bot or spammer. If you encounter two consecutive rejections, stop immediately and escalate to a human contributor.