contribute-to-template

Resolve project-template differences with DISCARD, MERGE, CONTRIBUTE, and KEEP decisions.

Updated Mar 28, 2025
One-click install
npx skills add https://github.com/gileck/app-template-ai --skill contribute-to-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contribute-to-template
Source: https://github.com/gileck/app-template-ai/tree/main/.ai/skills/template/contribute-to-template
Command: npx skills add https://github.com/gileck/app-template-ai --skill contribute-to-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and resolves differences between a project and its template to achieve full synchronization.

Core Features & Use Cases

  • Resolve per-file diffs between the project and the template to ensure alignment.
  • Manage per-file resolutions with DISCARD, MERGE, CONTRIBUTE, and KEEP to tailor outcomes for both sides.
  • Generate a structured message for the template agent and update template synchronization config (e.g., .template-sync.json) to reflect project-specific files.
  • Preview changes and guide the user through a safe, auditable synchronization process.

Quick Start

  1. Run the resolve-and-sync workflow to compare your project with the template.
  2. Review each file's diff and choose DISCARD / MERGE / CONTRIBUTE / KEEP.
  3. Copy the generated message for the template agent and follow the template's review process.
  4. After template commits, run yarn sync-template to verify alignment.

Frequently Asked Questions about contribute-to-template

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

FAQPage Schema
How do I sync my project with a template repository?

You sync a project with a template by running the resolve-and-sync workflow to compare diffs, then choosing DISCARD, MERGE, CONTRIBUTE, or KEEP per file to achieve full synchronization across both repositories.

What is the best way to resolve diffs between a project and its template?

Resolving template diffs involves reviewing each file's difference and applying per-file resolutions: DISCARD to drop changes, MERGE to combine, CONTRIBUTE to push back, or KEEP to retain the current project state.

How do I contribute project updates back to a git template repository?

To contribute updates back to a git template, select CONTRIBUTE for project-specific files, which generates a structured message for the template agent and updates the .template-sync.json configuration for the template's review process.

How does template synchronization config work for project-specific files?

Template synchronization config works by updating the .template-sync.json file to reflect project-specific files, ensuring future sync operations skip or handle them correctly based on your chosen DISCARD, MERGE, CONTRIBUTE, or KEEP resolutions.

Can I preview changes before merging a project with its template?

Yes, you can preview changes before merging. The synchronization process guides you through a safe, auditable workflow where you review each file's diff and select per-file resolutions before any updates are applied to either the project or the template.

What do I do after contributing updates to a template repository?

After contributing updates to a template, copy the generated structured message for the template agent, follow the template's review process, and once commits are made, run yarn sync-template to verify alignment between the project and template.