upstream-skill

To document local skill changes for upstream contribution, you need to track modifications using Git and generate per-skill changelogs in a specific Markdown format detailing additions, modifications, or deletions to facilitate integration back into the monorepo.

Generating a changelog for modified skills requires tracking Git changes within your local skill set and creating detailed, upstream-ready Markdown entries that document each modification, addition, or deletion per skill.

Yes, Git is required for change detection. The skill uses Git to identify modifications, additions, or deletions within local skill installations and generates per-skill changelogs to facilitate upstream integration.

Change tracking works by using Git to identify modifications, additions, or deletions within the local skill set. It then generates detailed per-skill changelogs adhering to a specific Markdown format to clearly document those customized changes.

Yes, this skill tracks modifications, additions, and deletions within local skill installations, generating upstream-ready changelogs in a specific Markdown format to facilitate integration of those changes back into the central project repository.

Changelog entries must adhere to a specific Markdown format. The skill generates detailed, upstream-ready per-skill changelogs documenting modifications, additions, or removals to ensure consistency and facilitate collaboration.