repo-refresh-skill

Name: repo-refresh-skill
Availability: InStock
Author: oceaneyeff

Refresh repository slow variables from verified, baseline-traceable worktrack evidence.

29|2|Updated Mar 2, 2026

Search Tags:#state transition #repository refresh #verified evidence #worktrack closure #baseline tracing #handover report

Ready to run

npx skills add https://github.com/OceanEyeFF/servo --skill repo-refresh-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-refresh-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/repo-refresh-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill repo-refresh-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents incorrect or unverified worktrack outputs from being blindly copied into repo-level truth, and instead refreshes the repository’s slow variables only from verified, traceable evidence.

Core Features & Use Cases

Verified-evidence-only repo refresh: Updates repo-level evaluations from gate-validated findings and baseline-traced checkpoints, blocking any unverified write paths.
Worktrack-to-Repo closure handoff: Acts as the end of the worktrack loop and the start of the repo loop by writing a structured, programmer-reviewable handover.
Milestone backlog integration: Updates .servo/repo/worktrack-backlog.md and marks milestone backlog completion (while leaving milestone status updates to the next observe phase).

Quick Start

Ask the agent to run repo-refresh-skill to refresh the repository snapshot truth using the verified close-worktrack evidence and generate an approval-ready handover report.

Frequently Asked Questions about repo-refresh-skill

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

FAQPage Schema

How do I safely update repository truth after a worktrack closes?▼

A repository refresh prevents incorrect or unverified worktrack outputs from being blindly copied into repo-level truth by updating slow variables exclusively from gate-validated findings and baseline-traced checkpoints.

What is baseline tracing in repository state transitions?▼

Baseline tracing in repository state transitions enforces strict provenance from close handoff evidence, blocking any unverified or non-traceable write target updates to maintain repo-level truth integrity.

How do I generate an approval-ready handover report for repo refresh?▼

Generate an approval-ready handover report by running the repo refresh process, which writes a structured, programmer-reviewable handover documenting the transition from worktrack loop to repo loop using verified evidence.

Can I update milestone status during a worktrack closure handoff?▼

During a worktrack closure handoff, you can update the milestone backlog file and mark completions, but the actual milestone status updates are deferred to the next observe phase in the control loop.

How does a repo refresh handle unverified write paths?▼

A repo refresh handles unverified write paths by strictly blocking them, ensuring that repository-level evaluations and slow variables only update from gate-validated findings and baseline-traced checkpoints.

When do I need to refresh repo-level slow variables in a control loop?▼

You need to refresh repo-level slow variables in a control loop when the WorktrackScope has finished and RepoScope must update before the next repo action, marking the end of the worktrack loop.