skills.rest
w-winter
w-winterCOMMUNITY
Explore all skills by this author →
𝕏@ambigrammarianGitHub

repoprompt-tool-guidance-refresh

Track RepoPrompt MCP/CLI version changes and generate diffs to rp-tool-defs.

122|16|Updated Jan 19, 2026
Search Tags:#automation#documentation#MCP#rp-cli#diff-generation#version-tracking#repo-prompt
One-click install
npx skills add https://github.com/w-winter/dot314 --skill repoprompt-tool-guidance-refresh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repoprompt-tool-guidance-refresh
Source: https://github.com/w-winter/dot314/tree/main/skills/repoprompt-tool-guidance-refresh
Command: npx skills add https://github.com/w-winter/dot314 --skill repoprompt-tool-guidance-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rp-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams keep RepoPrompt MCP/CLI guidance aligned with evolving tool definitions by tracking version updates, generating CLI/help artifacts, and surfacing diffs for MCP documentation updates.

Core Features & Use Cases

  • Automated version tracking for RepoPrompt MCP CLI across upgrades.
  • Diff generation and artifact publication to rp-tool-defs for CLI/help changes.
  • Workflow assistance for MCP/documentation refresh during version bumps.

Quick Start

  • Run ./track-rp-version.sh --pre before upgrading RepoPrompt to capture baseline.
  • After upgrading, run ./track-rp-version.sh --post to capture the new version and generate diffs.
  • Review generated diffs in rp-tool-defs and align MCP prompts and docs accordingly.

Frequently Asked Questions about repoprompt-tool-guidance-refresh

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

FAQPage Schema
How do I track RepoPrompt MCP CLI changes during a version upgrade?▼

Track RepoPrompt MCP CLI changes by running track-rp-version.sh with the --pre flag before upgrading to capture a baseline, then using --post after upgrading to generate diffs and artifacts in rp-tool-defs.

What is the best way to automate MCP tool documentation updates after a CLI version bump?▼

Automate MCP documentation updates by capturing CLI help diffs and publishing artifacts to rp-tool-defs, which provides the downstream data needed to align MCP prompts and docs with the new version.

Do I need rp-cli installed to generate diffs for RepoPrompt tool definitions?▼

Yes, you need the rp-cli tool installed locally along with the track-rp-version.sh script to execute version tracking and generate CLI help diffs for RepoPrompt.

Can I use this workflow to surface CLI help differences for MCP documentation refresh?▼

Yes, the workflow surfaces CLI help differences by generating diff artifacts during the post-upgrade phase, allowing you to review changes and align MCP tool definitions accordingly.

What limitations exist when automating RepoPrompt version tracking across upgrades?▼

The automation is limited to local execution requiring track-rp-version.sh and rp-cli, and it outputs artifacts exclusively to the rp-tool-defs directory for downstream documentation alignment.

Related Skills

Explore More Software Engineering Skills→
lubusINlubusIN
48

frappe-project-triage

Identify Frappe project type, installed apps, version, and tooling.

Official
Intermediate
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
base44base44
86

sync-cli-skill

Detect changes between local and stored Base44 CLI source via git-diff.

Official
Advanced