contribute

Name: contribute
Availability: InStock
Author: ChazzCoin

Package local kit-managed file edits into pull requests for the upstream claude-kit repository.

Updated Apr 28, 2026

Search Tags:#git #drift-detection #contribute #pull-request #claude-kit #foundation.json

Ready to run

npx skills add https://github.com/ChazzCoin/claude-kit --skill contribute-chazzcoin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contribute
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/contribute
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill contribute-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to push local, kit-managed improvements back to the upstream claude-kit repository by packaging edits into pull requests, closing the kit ↔ project loop.

Core Features & Use Cases

Detects drift in kit-managed files since the last sync and classifies edits as portable improvements vs project-specific overrides.
Drafts PR titles and bodies, grouping related changes into coherent PRs for upstream review.
Applies changes only after explicit confirmation, and can update overrides in foundation.json when necessary.

Quick Start

Invoke the contribute skill after refining a kit-managed file to generate a PR upstream.

Frequently Asked Questions about contribute

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

FAQPage Schema

How do I push local claude-kit file edits upstream as a pull request?▼

To push local claude-kit file edits upstream, you invoke the contribute skill after refining a kit-managed file, which detects drift and packages portable improvements into a drafted pull request for upstream review.

How does drift detection distinguish portable improvements from project-specific overrides?▼

Drift detection compares your local kit-managed file versions against the pinned_sha in foundation.json, classifying edits as portable improvements for upstream contribution or project-specific overrides to retain locally.

Do I need a foundation.json file to contribute local kit edits upstream?▼

Yes, you need a foundation.json file because the contribute skill reads it to locate the upstream claude-kit repository, branch, and pinned_sha needed to compare versions and draft pull requests.

Can I group related local kit changes into a single pull request for upstream review?▼

Yes, the contribute skill drafts PR titles and bodies by grouping related local kit edits into coherent pull requests, ensuring your portable improvements are packaged logically for upstream review.

When should I not use automated pull requests for kit file contributions?▼

You should not use automated pull requests for kit file contributions when your local edits are project-specific overrides, as the drift detection mechanism distinguishes these from portable improvements meant for upstream.