React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
A skill your agent uses whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project.
Install Workthrough Tracker
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FrancoGiudans/Capsulyric workthrough-tracker --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workthrough-tracker .claude/skills/workthrough-tracker && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .claude/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-trackerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FrancoGiudans/Capsulyric workthrough-tracker --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/workthrough-tracker .agents/skills/workthrough-tracker && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .agents/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FrancoGiudans/Capsulyric workthrough-tracker --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/workthrough-tracker .cursor/skills/workthrough-tracker && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .cursor/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FrancoGiudans/Capsulyric.git --path .agents/skills/workthrough-tracker--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FrancoGiudans/Capsulyric workthrough-tracker --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/workthrough-tracker .gemini/skills/workthrough-tracker && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .gemini/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FrancoGiudans/Capsulyric workthrough-trackerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/workthrough-tracker .github/skills/workthrough-tracker && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .github/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FrancoGiudans/Capsulyric workthrough-tracker --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FrancoGiudans/Capsulyric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/workthrough-tracker .opencode/skills/workthrough-tracker && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "workthrough-tracker" agent skill from https://github.com/FrancoGiudans/Capsulyric/tree/main/.agents/skills/workthrough-tracker into .opencode/skills/workthrough-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workthrough-tracker", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
workthrough-tracker- GitHub stars
- 202
- Token cost
- ~748 tokens
- SKILL.md length
- 123 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project.
- Works in 4 steps: 开展工作 / 制定计划时 (Start of Task / Planning) → 执行过程中 / 完成计划中的一步时 (During Execution /… → 完成一项工作时 (Task Completion) → …
- Starting any new work
- SKILL.md covers 核心规则与流程, 文件命名规范, 记录模板 (Template) and 注意事项
- Calls git
What it does
Workthrough Tracker is an agent skill from FrancoGiudans/Capsulyric. Use this skill whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project. Guides creating and maintaining work progress logs named as workthrough/YYYY-MM-DD<工作名称.md (e.g., 2026-08-01修复xxxx.md), and automatically committing changes to the dedicated workthrough/ Git repository upon completing work.
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages. It works with Git. The repository describes itself as: 提供基于Live Update和小米超级岛机制的状态栏歌词。 The licence is GPL-3.0.
When your agent uses it
- Starting any new work
- Formulating a development plan
- Completing individual tasks/steps in this project
Example prompts
- “/workthrough-tracker”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit dd020bc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Workthrough Tracker loads about 748 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 123 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from FrancoGiudans/Capsulyric at commit dd020bc, republished under its GPL-3.0 licence (© FrancoGiudans). 123 words, ~748 tokens.
Download SKILL.mdSave it as
.claude/skills/workthrough-tracker/SKILL.md (or your agent's skills folder).- name
- workthrough-tracker
- description
- Use this skill whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project. Guides creating and maintaining work progress logs named as `workthrough/YYYY-MM-DD_<工作名称>.md` (e.g., `2026-08-01_修复xxxx.md`), and automatically committing changes to the dedicated `workthrough/` Git repository upon completing work.
Workthrough Tracker (工作记录追踪)
本 Skill 用于规范在开展工作、制定计划以及完成工作步骤时的记录流程，确保在 workthrough/ 目录下按日期及具体工作名称独立记录所有工作进度与变更。
核心规则与流程
1. 开展工作 / 制定计划时 (Start of Task / Planning)
- 确定文件名：
- 确认当天日期（格式：
YYYY-MM-DD，例如2026-08-23）。 - 根据当前任务提取精炼的工作名称（例如
修复歌词解析异常、适配Miuix毛玻璃效果）。 - 文件路径为：
workthrough/YYYY-MM-DD_<工作名称>.md（例如workthrough/2026-08-23_修复歌词解析异常.md）。
- 确认当天日期（格式：
- 创建或继续记录：
- 若该工作记录文件不存在，在
workthrough/目录下创建该文件。 - 写入标题、任务目标与背景、详细实施计划清单（带复选框）。
- 若是在同一次任务的后续阶段继续推进，则在现有文件对应章节继续完善。
- 若该工作记录文件不存在，在
2. 执行过程中 / 完成计划中的一步时 (During Execution / Step Completion)
- 即时记录：每完成一个子步骤或遇到关键决策/调试结果时，立即更新对应的
workthrough/YYYY-MM-DD_<工作名称>.md文件，不要等到所有工作全部结束才记录。 - 更新内容：
- 将计划列表中的复选框标记为已完成：
- [x] <步骤名称>。 - 记录所修改/新建的关键文件路径及改动点。
- 记录测试与验证结果（编译状态、单元测试、运行表现等）。
- 记录遇到的问题及解决方案。
- 将计划列表中的复选框标记为已完成：
3. 完成一项工作时 (Task Completion)
- 汇总本次任务完成情况。
- 更新任务状态为
[已完成]或标明后续待办事项。
4. 完成所有工作后自动提交 Git Commit (Auto Git Commit)
workthrough/目录是一个独立的 Git 仓库（已被根目录.gitignore忽略，内部拥有独立的.git）。- 必须执行：在完成当前任务的所有开发与记录工作后，立即自动在
workthrough/中提交一个 Git Commit，简要说明完成了什么工作。 - 执行命令：
bash git -C workthrough add . git -C workthrough commit -m "docs: 记录完成<工作名称>的工作进度与变更" - Commit Message 示例：
git -C workthrough commit -m "docs: 记录完成 2026-08-23_适配Miuix毛玻璃效果"git -C workthrough commit -m "docs: 记录完成 2026-08-01_修复xxxx"
文件命名规范
- 目录：
workthrough/ - 文件名格式：
YYYY-MM-DD_<工作名称>.md- 示例 1：
workthrough/2026-08-01_修复xxxx.md - 示例 2：
workthrough/2026-08-23_适配Miuix下拉菜单毛玻璃效果.md - 示例 3：
workthrough/2026-08-23_重构LyricParser解析器.md
- 示例 1：
记录模板 (Template)
workthrough/YYYY-MM-DD_<工作名称>.md 模板
# 2026-08-23 修复歌词解析异常 工作记录
---
## 1. 目标与背景
- 简要描述本次任务需要实现的功能、修复的问题或重构的目标。
---
## 2. 实施计划 (Plan)
- [ ] 步骤 1: 定位解析异常引发原因
- [ ] 步骤 2: 修复正则表达式与边界处理逻辑
- [ ] 步骤 3: 补充单元测试并验证编译
---
## 3. 执行过程与变更记录 (Execution Log)
- **[14:35] 步骤 1 完成**
- 排查结果：在特定时间戳格式下出现越界错误。
- **[14:50] 步骤 2 完成**
- 修改文件：`app/src/main/java/.../LyricParser.kt`
- 变更说明：优化时间标签正则匹配，增加安全校验。
- **[15:10] 步骤 3 完成**
- 修改文件：`app/src/test/java/.../LyricParserTest.kt`
- 变更说明：新增多时间标签边界测试用例。
---
## 4. 验证与测试 (Verification)
- 编译状态：BUILD SUCCESSFUL
- 单元测试：`./gradlew testDebugUnitTest` 全部通过 (12/12)
- 运行验证：真机/模拟器测试解析正常。
---
## 5. 总结与状态 (Summary)
- 当前状态：[已完成]
- 遗留事项：无注意事项
- 按工作命名：每项独立的工作/任务使用清晰描述性名称命名文件（
YYYY-MM-DD_<工作名称>.md），便于按事件追溯。 - 原子性更新：每完成一个计划步骤，应立即同步更新文档，保证记录实时准确。
- 路径准确：记录文件变更时，使用项目相对路径（例如
app/src/main/java/...或docs/...），方便追溯。 - 自动提交：全部工作完成后，务必自动在
workthrough/中执行 git commit 提交当次记录。
© FrancoGiudans, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/workthrough-tracker of FrancoGiudans/Capsulyric.
Open the folder on GitHubat commit dd020bc
Compare with similar skills
Workthrough Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Workthrough Tracker this skillFrancoGiudans/Capsulyric | 202 | — | ~748 | Automated safety check: Pass | GPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
More from FrancoGiudans/Capsulyric
Miuix UI
FrancoGiudans/Capsulyric
Build, review, and refactor Compose Miuix UI in IslandLyrics using Miuix 0.9.3 conventions, the app blur wrapper stack, theme tokens, popup-host rules, and compile-first verification.
Related
Works with
Categories
Questions about Workthrough Tracker
What does Workthrough Tracker do?
A skill your agent uses whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project. Workthrough Tracker is an agent skill from FrancoGiudans/Capsulyric. Use this skill whenever starting any new work, formulating a development plan, or completing individual tasks/steps in this project.
When should I use Workthrough Tracker?
Workthrough Tracker fits situations like: starting any new work; formulating a development plan; completing individual tasks/steps in this project.
How do I install Workthrough Tracker in Claude Code?
Run `npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a claude-code`. Or copy the skill folder (.agents/skills/workthrough-tracker in FrancoGiudans/Capsulyric) into .claude/skills/workthrough-tracker in your project. Claude Code loads it when a task matches its description.
How do I install Workthrough Tracker in Codex?
Run `npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a codex`. Or copy the skill folder (.agents/skills/workthrough-tracker in FrancoGiudans/Capsulyric) into .agents/skills/workthrough-tracker in your project. Codex loads it when a task matches its description.
Can I use Workthrough Tracker in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FrancoGiudans/Capsulyric --skill workthrough-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workthrough-tracker, .gemini/skills/workthrough-tracker, .github/skills/workthrough-tracker and .opencode/skills/workthrough-tracker in your project.
What does Workthrough Tracker need to run?
Going by SKILL.md and its folder, Workthrough Tracker needs the command-line tools its instructions call (git).
Does Workthrough Tracker access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Workthrough Tracker safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Workthrough Tracker use?
Workthrough Tracker is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workthrough Tracker use?
About 748 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Workthrough Tracker?
Skills that share tags, products or a category with Workthrough Tracker: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workthrough Tracker?
FrancoGiudans (a GitHub user) maintains it in FrancoGiudans/Capsulyric, which has 202 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: FrancoGiudans/Capsulyric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.