skills.rest
bhanford9
bhanford9COMMUNITY
Explore all skills by this author →
GitHub

update-copilot-tools

Sync local Copilot Tools with the remote repository and surface follow-up actions.

1|Updated Apr 14, 2026
Search Tags:#automation#git#hooks#sync#pull#settings#lessons-learned
One-click install
npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill update-copilot-tools
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-copilot-tools
Source: https://github.com/bhanford9/vs-code-copilot-tools/tree/main/skills/update-copilot-tools
Command: npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill update-copilot-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs the local Copilot Tools setup with the remote repository and surfaces required follow-up actions to keep tools in sync across machines.

Core Features & Use Cases

  • Pulls the latest copilot-tools repo, rebases, and records changes for review.
  • Detects and surfaces manual actions (e.g., settings.json merges, hook path validation) that require user confirmation.
  • Generates a concise summarization of changes and ends with a Lessons Learned entry to improve future sessions.
  • Handles edge cases such as uncommitted local changes, conflicts, and zero-change scenarios with clear guidance.

Quick Start

Run the update-copilot-tools skill after teammates push changes to pull, analyze, and surface required follow-ups.

Frequently Asked Questions about update-copilot-tools

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

FAQPage Schema
How do I sync local Copilot Tools settings after my teammates push updates?▼

To sync local Copilot Tools settings, run the update-copilot-tools task to pull the latest repository changes via rebase, classify modified files, and surface a summarized action plan for required manual follow-ups.

What happens if I have uncommitted local changes when pulling copilot-tools updates?▼

When uncommitted local changes are detected during a copilot-tools sync, the process pauses to provide clear guidance, preventing conflicts before performing a rebase pull and enumerating changed files for review.

How does this approach handle settings.json merges and hook path validation?▼

Settings.json merges and hook path validations are classified as manual actions during the sync, prompting for explicit user confirmation to ensure path integrity and correct setting configurations.

Can I track lessons learned from syncing git hooks and settings across machines?▼

Yes, the sync process ends by generating a LessonsLearned entry, capturing insights from the current session to improve future repository updates and manual action handling across machines.

What is the best way to review changed files after a rebase pull on copilot-tools?▼

The best way to review changed files is using the built-in diff enumeration, which classifies changes and presents a concise summarization of required follow-up actions like settings merges or path validations.

Does update-copilot-tools handle zero-change scenarios when pulling the remote repository?▼

Yes, zero-change scenarios are handled with clear guidance during the pull process, ensuring the local Copilot Tools setup remains in sync without unnecessary prompts when no new changes are found.

Related Skills

Explore More Software Engineering Skills→
yulonglinyulonglin
11

commit-push-sync

Automate git commit, pull with rebase, and push workflows.

Community
Advanced
shdzhangshdzhang

asq-followup

Automates post-meeting follow-up by drafting emails, updating SFDC CAST notes, and creating calendar invites.

Community
Advanced
huynguyenhhuynguyenh
3

hnh-setup

Clone a GitHub repository and restore Claude Code workspace files.

Community
Advanced
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced