skills.rest
vllm-project
vllm-projectOFFICIAL
Explore all skills by this author →
GitHub

project-change

Implements focused repository changes when no specialized workflow applies.

5.5k|880|Updated Aug 26, 2025
Search Tags:#Validation#Repository#code change#REFACTOR#CI gate#fallback workflow#agent report
One-click install
npx skills add https://github.com/vllm-project/semantic-router --skill project-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-change
Source: https://github.com/vllm-project/semantic-router/tree/main/tools/agent/skills/project-change
Command: npx skills add https://github.com/vllm-project/semantic-router --skill project-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a coding task does not match any specialized workflow, developers need a disciplined fallback process that keeps changes scoped, validated, and consistent with repository contracts instead of ad-hoc edits.

Core Features & Use Cases

  • Fallback Change Routing: Handles features, fixes, refactors, documentation updates, and subsystem-local tasks selected by changed-file routing.
  • Contract-Aware Implementation: Reads the agent report and nearest AGENTS.md to locate affected contracts before editing code.
  • Scoped Validation: Runs the smallest relevant checks via make agent-report and make agent-ci-gate, widening validation only when behavior crosses surfaces.
  • Use Case: A developer receives a bug fix touching files in one subsystem with no dedicated workflow; this Skill guides reading the agent report, implementing the fix within its natural boundary, and running the minimal CI gate.

Quick Start

Ask the agent to implement the requested repository change using the project-change fallback workflow and validate it with the smallest relevant checks.

Frequently Asked Questions about project-change

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

FAQPage Schema
How do I handle a repository change with no specialized workflow?▼

Use the project-change fallback workflow: read the agent report and nearest AGENTS.md, implement the change within its natural boundary, then run the smallest relevant checks. Widen validation only when behavior or contracts cross surfaces.

What commands validate a focused code change in this repository?▼

Run make agent-report with ENV and CHANGED_FILES set to generate the routing report, then make agent-ci-gate with the same CHANGED_FILES to execute the relevant CI gate for the touched files.

When should validation be widened beyond the smallest checks?▼

Widen validation only when the change alters behavior or contracts that cross subsystem surfaces. For changes contained within one boundary, the smallest relevant checks named by the agent report are sufficient.

When should I stop instead of completing a change?▼

Stop only for a real product decision, missing authority, or an unavailable environment that prevents meaningful progress. The agent report guides finding affected contracts but does not prohibit necessary implementation work.

Does a focused change require updating tests and documentation?▼

Yes, when the contract genuinely crosses a boundary, update dependent code, tests, docs, or tracked debt alongside the change. Keep the change focused but keep affected contracts aligned.

Related Skills

Explore More Software Engineering Skills→
guhans6guhans6

refresh-project-agent-routing

Refresh project agent routing contracts with delta-only file changes.

Community
Advanced
vllm-projectvllm-project
5.1k

cross-stack-bugfix

Diagnoses and fixes bugs spanning multiple layers with coordinated changes.

Official
Advanced
ezagent42ezagent42
1

contract-check

Analyze contract diffs and report impacted tasks and code paths.

Official
Advanced
albertbuchardalbertbuchard
23

forge-hermes

Expose Movement, Life Force, and Workbench routes for Hermes-Forge integration.

Community
Advanced