downstream-skill

Synchronize field-tested skill changes from downstream Basecamp installations into monorepo skill definitions.

4|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/forwardimpact/monorepo --skill downstream-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: downstream-skill
Source: https://github.com/forwardimpact/monorepo/tree/main/.claude/skills/downstream-skill
Command: npx skills add https://github.com/forwardimpact/monorepo --skill downstream-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of integrating improvements and fixes discovered in deployed "Basecamp" installations back into the main "monorepo" codebase, ensuring the canonical skill definitions remain up-to-date and benefit from real-world usage.

Core Features & Use Cases

  • Changelog Analysis: Automatically parses changelogs from downstream installations to identify modifications.
  • Change Evaluation: Assesses whether downstream changes are general improvements suitable for upstream integration or installation-specific customizations.
  • Upstream Integration: Applies approved changes to the canonical skill templates and associated data files within the monorepo.
  • Use Case: After a new feature is tested and refined in a live "Basecamp" installation, this skill can be used to review the changes made in that installation's skill files and incorporate them back into the main project, making the new feature available to all future installations.

Quick Start

Run this skill to check for and incorporate any field-tested skill changes from your downstream installations back into the monorepo.

Frequently Asked Questions about downstream-skill

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

FAQPage Schema
How do I sync downstream skill changes back into a monorepo?

This skill synchronizes field-tested skill changes by parsing per-skill changelogs from Basecamp installations, evaluating modifications against inclusion criteria, and integrating approved updates into the monorepo's canonical skill definitions.

What is the best way to evaluate if field-tested skill modifications should be integrated upstream?

Evaluating field-tested skill modifications requires analyzing downstream changelogs to distinguish between general improvements suitable for upstream integration and installation-specific customizations that should remain isolated to their Basecamp deployment.

Can I use changelog analysis to update canonical skill templates from a deployed Basecamp installation?

Yes, changelog analysis automatically parses modifications from deployed Basecamp installations, evaluates them against general applicability criteria, and applies approved changes to canonical skill templates and capability data files within the monorepo.

Does this skill require specific dependencies to manage upstream integration in a monorepo?

No specific dependencies are required. The skill operates independently using its internal scripts and references to sync field changes upstream from Basecamp installations into the monorepo's canonical skill definitions.

When should I avoid syncing field changes from downstream Basecamp installations?

You should avoid syncing field changes when downstream modifications are installation-specific customizations rather than general improvements, as these fail the inclusion criteria for upstream integration into canonical skill templates and capability data.