gsd-update

Synchronize Manus skills with upstream get-shit-done via diff analysis and validation.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/da-moon/manus-skills --skill gsd-update-da-moon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-update
Source: https://github.com/da-moon/manus-skills/tree/main/skills/gsd-update
Command: npx skills add https://github.com/da-moon/manus-skills --skill gsd-update-da-moon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns Manus GSD skills with upstream get-shit-done to prevent drift and manual drift across multiple skills.

Core Features & Use Cases

  • Detects changes in upstream GSD and maps them to the correct Manus skill(s).
  • Plans and coordinates updates across affected skills, including version tracking and validation.
  • Supports safe, batched pushes to keep all skills in sync with upstream.

Quick Start

Run the update workflow to synchronize all Manus GSD skills with the latest upstream release.

Frequently Asked Questions about gsd-update

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

FAQPage Schema
How do I sync local skills with upstream repository updates?

To sync local skills with upstream updates, this workflow detects differences, maps upstream changes to the correct skill, and applies batched pushes to keep all skills consistent. It ensures safe synchronization across affected commands, workflows, agents, and templates.

What is the best way to track version changes across multiple skills?

Tracking version changes across multiple skills requires diff analysis and automated validation. This process enforces scoped updates, maps upstream changes to the correct skill, and ensures consistency before pushing any modifications.

How does diff analysis work for planning skill refactors?

Diff analysis for planning skill refactors works by detecting upstream changes, mapping them to the correct Manus skill, and coordinating updates across affected skills. It enforces scoped updates and validates consistency before applying changes.

Can I batch update commands, workflows, agents, and templates without drift?

Yes, you can batch update commands, workflows, agents, and templates without drift. The workflow coordinates cross-skill updates, enforces scoped changes, and runs automated validation to ensure consistency before pushing.

When should I use automated validation for skill synchronization?

You should use automated validation for skill synchronization when applying upstream changes across multiple skills. It ensures consistency, verifies scoped updates, and prevents drift before pushing batched modifications to your repositories.