contribute

Prepare and verify code contributions for Pulp and Forge repositories.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill contribute-generous-corp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contribute
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/contribute
Command: npx skills add https://github.com/Generous-Corp/pulp --skill contribute-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, cmake, diff-cover.

What problem does it solve?

This Skill removes the guesswork from contributing to the Pulp or Forge repositories by providing a standardized, maintainable workflow that ensures your changes are accepted by maintainers without unnecessary rework.

Core Features & Use Cases

  • Standardized Handoff: Generates a structured handoff document including verification, provenance, and unverified gaps.
  • Local Validation: Guides you through running the contributor check script and verifying test failures locally without needing complex maintainer infrastructure.
  • Use Case: You have fixed a bug in the Pulp core and want to submit it; use this Skill to verify your fix, run the required gates, and format your submission so a maintainer can land it immediately.

Quick Start

Use the contribute skill to prepare my current changes for submission to the Pulp repository.

Frequently Asked Questions about contribute

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

FAQPage Schema
How do I prepare a Pulp code contribution for maintainer review?▼

Preparing a Pulp contribution involves running local validation gates, verifying test coverage, and generating a structured handoff document so maintainers can land your changes without unnecessary rework.

What is included in a standardized code contribution handoff document?▼

A standardized handoff document includes verification results, code provenance, and unverified gaps to ensure your submission meets project standards for test coverage, documentation, and licensing.

Do I need maintainer infrastructure to run Pulp contributor check scripts locally?▼

No, you do not need complex maintainer infrastructure to validate Pulp contributions locally; this skill guides you through running the contributor check script and verifying test failures without internal tooling.

How do I verify test coverage and code review gates before submitting to Pulp?▼

You can verify test coverage and code review gates by running the local contributor check script through this skill, which validates your changes meet Pulp project standards before submission.

Can I use diff-cover and cmake to validate code submissions for Forge repositories?▼

Yes, this skill standardizes code preparation for Forge repositories using dependencies like diff-cover and cmake to validate test coverage and ensure submissions meet project gate requirements.