ccontribute

Automate open-source contribution workflows from conventions to pull request generation.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill ccontribute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccontribute
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/ccontribute
Command: npx skills add https://github.com/joshft/correctless --skill ccontribute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors align their changes with a target project's conventions, ensuring that open-source contributions resemble those authored by maintainers and pass review unstyled.

Core Features & Use Cases

  • Learn project conventions by reading CONTRIBUTING guides, code owners, and contribution templates before making changes.
  • Plan and generate a PR that matches the repository's patterns (branch naming, commit messages, testing requirements, and review expectations).
  • Maintain progress visibility during the workflow with step-by-step status updates and reviewer handoffs.

Quick Start

Invoke with: /ccontribute <issue number or description of what to change>.

Frequently Asked Questions about ccontribute

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

FAQPage Schema
How do I align my pull request with open-source project conventions?

To align your pull request with project conventions, automate the contribution workflow by reading CONTRIBUTING guides, applying branch naming rules, and generating commits that match maintainer expectations before submitting code.

What's the best way to learn repository conventions before contributing to a codebase?

Learning repository conventions involves reading CONTRIBUTING guides, code owners, and contribution templates before making changes to ensure your open-source contributions resemble those authored by maintainers.

How do I generate a pull request that passes code review on the first try?

Generating a pull request that passes code review requires matching repository patterns for branch naming, commit messages, and testing requirements, guided by step-by-step planning and mandatory progress updates.

Can I use an automated workflow for both bug fixes and feature work across diverse codebases?

Yes, an automated contribution workflow applies to both bug fixes and feature work across diverse codebases, guiding the process from learning conventions to generating a compliant pull request.

How do I maintain progress visibility during an open-source contribution workflow?

Maintaining progress visibility during a contribution workflow requires implementing step-by-step status updates and reviewer handoffs to track the process from issue resolution to pull request generation.