harness-contribute

Create a feature branch and pull request for harness repository improvements.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/sizukutamago/claude-code-harness --skill harness-contribute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-contribute
Source: https://github.com/sizukutamago/claude-code-harness/tree/main/.claude/skills/harness-contribute
Command: npx skills add https://github.com/sizukutamago/claude-code-harness --skill harness-contribute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates contributing reusable improvements from a project back into the harness repository by creating a feature branch, mapping and applying changes to harness paths, testing the update, and opening a pull request for review.

Core Features & Use Cases

  • File mapping: Maps project-side files (agents, skills, rules, hooks) to the corresponding harness repository paths and treats non-matching files as new additions.
  • Judgement workflow: Helps determine whether a change is generic (worth upstreaming) or project-specific, and mandates human confirmation when needed.
  • Branch, test, PR flow: Creates a feature branch, applies templated changes preserving Jinja where required, tests them via copier update, and prepares a PR with context and test results.
  • Use case: During a retrospective you discover a rules or skill improvement; use this Skill to transform that improvement into a tested harness template and propose it upstream.

Quick Start

Use the harness-contribute skill to create a harness feature branch, apply mapped changes from my project, run copier update to test them, and open a PR explaining what changed and why.

Frequently Asked Questions about harness-contribute

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

FAQPage Schema
How do I contribute project improvements back to a copier template repository?

To contribute project improvements back to a copier template repository, this Skill automates creating a feature branch, mapping project files to harness template paths, testing via copier update, and opening a pull request.

What is the process for upstreaming rule fixes and agent changes discovered during a retrospective?

Upstreaming rule fixes and agent changes discovered during a retrospective involves mapping those project-side files to the harness repository, preserving Jinja templating, running tests, and proposing the generic improvements upstream for review.

Do I need a .copier-answers.yml file to automate opening a pull request for harness updates?

Yes, you need a .copier-answers.yml file to automate opening a pull request for harness updates, as it identifies the harness source and allows the Skill to map and apply changes to the correct template repository.

How do I map project files to harness template paths when preparing a copier update?

Mapping project files to harness template paths matches existing agents, skills, rules, and hooks to their corresponding repository locations, while treating non-matching files as new additions before applying changes and testing.

When should I not upstream a local project change to the harness template?

You should not upstream a local project change to the harness template when the judgement workflow determines the modification is project-specific rather than generic, ensuring only broadly reusable improvements are proposed via pull request.