vector-cli-skill-sync

Sync CLI source changes into the vector-skill submodule.

2|4|Updated Jun 23, 2025
One-click install
npx skills add https://github.com/xrehpicx/vector --skill vector-cli-skill-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vector-cli-skill-sync
Source: https://github.com/xrehpicx/vector/tree/main/.agents/skills/vector-cli-skill-sync
Command: npx skills add https://github.com/xrehpicx/vector --skill vector-cli-skill-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures that changes in the CLI source files are reflected in the public vector-skill submodule, maintaining consistency between the CLI and the skill.

Core Features & Use Cases

  • CLI Change Reflection: Updates the vector-skill submodule when CLI commands, options, or behavior change.
  • Submodule Management: Commit and push changes to the vector-skill submodule after updating.
  • Use Case: When you modify the CLI source files, this skill helps you update the vector-skill submodule to ensure that the skill reflects the latest changes.

Quick Start

After modifying the CLI source files, run the following commands to update the skill:

cd packages/vector-skill
git add SKILL.md
git commit -m "Update skill to reflect CLI changes"
git push
cd ../..
git add packages/vector-skill
git commit -m "Update vector-skill submodule"
git push

Frequently Asked Questions about vector-cli-skill-sync

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

FAQPage Schema
How do I sync CLI source file changes with a public git submodule?

To sync CLI source file changes with a public git submodule, you commit and push updates inside the submodule directory, then commit and push the updated submodule reference in the parent repository.

When do I need to update a git submodule after modifying CLI commands?

You need to update a git submodule after modifying CLI commands when you want the public skill repository to reflect the latest behavior changes and maintain consistency across your development workflow.

What is the best way to manage submodule updates when CLI behavior changes?

The best way to manage submodule updates when CLI behavior changes is to enter the submodule directory, commit the modified skill files, push them, then update and push the submodule pointer in the parent repository.

Why does my parent repository not reflect the latest vector-skill submodule changes?

Your parent repository does not reflect the latest submodule changes because you likely updated files inside the submodule without committing and pushing the new submodule reference hash in the parent repository.