contrib-intake

Ingest fork-based pull requests and patches into isolated branches for validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a secure, structured workflow for maintainers to ingest, validate, and merge code contributions from outside the core team, ensuring that external code is safely vetted before entering the repository.

Core Features & Use Cases

  • Secure Adoption: Safely imports fork PRs or patches into isolated in-repo branches for verification.
  • Attribution Preservation: Ensures contributor authorship is maintained throughout the rebase and merge process.
  • Safety-First Validation: Enforces strict rules for running tests in isolated environments to prevent unauthorized code execution on sensitive build infrastructure.

Quick Start

Use the contrib-intake skill to adopt the contribution from pull request number 123 into a new branch named contrib/feature-name.

Frequently Asked Questions about contrib-intake

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

FAQPage Schema
How do I securely merge external pull requests into a main codebase?

Securely merge external pull requests by importing fork-based contributions into isolated in-repo branches for verification. This ensures all incoming code undergoes rigorous security checks and testing before integration into the main codebase.

What is the safest way to validate external code contributions without risking build infrastructure?

The safest way to validate external code contributions is to enforce strict rules for running tests in isolated environments. This prevents unauthorized code execution on sensitive build infrastructure during the vetting process.

How do I preserve contributor authorship when rebasing and merging a fork-based pull request?

Preserve contributor authorship during the rebase and merge process by using a structured contribution intake workflow. This maintains accurate attribution throughout the integration of external patches into the primary repository.

Can I ingest external patches into isolated branches for testing before a final git merge?

Yes, you can ingest external patches by adopting them into new isolated in-repo branches. This allows for structured verification and testing of external code contributions before they are merged into the main codebase.

When do I need a structured contribution intake workflow for my repository?

You need a structured contribution intake workflow when your repository requires maintainers to safely vet and merge code from outside the core team. It manages the lifecycle of fork-based pull requests and issues while enforcing security validation.