meta-contribute-back

Package skill adaptations into contribution branches in the agentic-workflow repository.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill meta-contribute-back
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-contribute-back
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/meta-contribute-back
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill meta-contribute-back

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of fragmented knowledge by allowing you to package and contribute custom skill adaptations from your local project back to the central agentic-workflow repository.

Core Features & Use Cases

  • Adaptation Packaging: Automatically identifies and formats pending skill adaptations for upstream review.
  • Branch Management: Safely creates contribution branches in the source repository to keep your changes organized.
  • Use Case: After refining a TDD workflow for your specific .NET stack, use this skill to push those improvements back to the main repository so other projects can benefit from your configuration.

Quick Start

Use the meta-contribute-back skill to package all pending adaptations for contribution to the source repository.

Frequently Asked Questions about meta-contribute-back

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

FAQPage Schema
How do I contribute custom workflow adaptations back to a central git repository?

Syncing project skill adaptations requires a configured workflow.json file and a tracked adaptations.md file to identify and stage pending changes for upstream review.

What is the best way to share stack-specific workflow improvements across multiple projects?

This skill solves fragmented knowledge by automating the creation of contribution files and git branches to push local project improvements upstream for review.

How does branch management work when syncing local skill learnings upstream?

Branch management for upstream syncing safely creates contribution branches in the source repository, keeping your custom skill adaptations organized and separate from the main codebase during the review process.

Do I need a workflow.json file to automate git contributions for DevOps knowledge-sharing?

Yes, automating git contributions for knowledge-sharing requires a configured workflow.json file alongside a tracked adaptations.md file to successfully identify, package, and stage pending skill changes for review.

Can I use this to package universal and stack-specific DevOps automation configurations separately?

Yes, you can package both universal and stack-specific skill adaptations from your local project, formatting pending workflow and automation improvements for upstream review in the source repository.