refresh-track

Regenerate Track shared view files and verify BOARD.md, TODO.md, and PROJECTS.md outputs.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Hugopeck/track --skill refresh-track
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refresh-track
Source: https://github.com/Hugopeck/track/tree/main/skills/todo
Command: npx skills add https://github.com/Hugopeck/track --skill refresh-track

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, gh, and includes scripts (resource) components.

What problem does it solve?

Regenerates Track's shared status views so a repository's board, todo list, and project overview stay synchronized during active work.

Core Features & Use Cases

  • Detects the available environment and chooses the right generation mode for full, offline, local, or user-forwarded runs.
  • Runs the Track view generator, verifies that BOARD.md, TODO.md, and PROJECTS.md were produced, and reports what changed.
  • Handles mid-session refreshes after task edits, PR updates, or repository state changes without manually rebuilding the views.

Quick Start

Ask the assistant to refresh Track for this repository and update BOARD.md, TODO.md, and PROJECTS.md with the latest view state.

Frequently Asked Questions about refresh-track

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

FAQPage Schema
How do I regenerate Track views for BOARD.md, TODO.md, and PROJECTS.md after task edits?

Regenerating Track views requires running the track-todo.sh script, which detects the environment, preserves user-supplied flags, and updates BOARD.md, TODO.md, and PROJECTS.md with the latest project state.

Do I need bash, git, and gh installed to refresh Track shared view files?

Yes, refreshing Track shared view files requires bash, git, and gh dependencies to detect the environment, run the view generator, verify output artifacts, and report failures with concrete next steps.

Can I update Track board and todo overviews during offline or local workflows?

Updating Track board and todo overviews works during full, offline, local, or forwarded workflows by detecting the available environment and choosing the correct generation mode to synchronize repository state.

Why are my Track markdown views not updating when repository state changes?

Track markdown views fail to update when track-todo.sh encounters environment detection issues or missing dependencies. The Skill surfaces these failures with concrete next steps to verify output artifacts and restore synchronization.

What is the best way to refresh Track project files without manually rebuilding views?

The best way to refresh Track project files without manual rebuilding is running an automated generation pass that applies user-supplied flags, executes track-todo.sh, and verifies that BOARD.md, TODO.md, and PROJECTS.md are produced.

When do I need to regenerate Track views in a GitHub repository?

Regenerating Track views is needed after task edits, PR updates, or repository state changes to keep board, todo list, and project overview markdown files synchronized during active development work.