Maintain Obsidian change-trace notes for Sandrone workspaces.
npx skills add https://github.com/ZhmYe/Sandrone --skill obsidian-change-trace
Please help me install this Agent Skill. Skill: obsidian-change-trace Source: https://github.com/ZhmYe/Sandrone/tree/main/skills/obsidian-change-trace Command: npx skills add https://github.com/ZhmYe/Sandrone --skill obsidian-change-trace
Keeps Sandrone workspaces navigable by turning scattered request, slice, review, PR, and recovery state into a clear Obsidian trace that a future agent can resume without digging through logs.
Ask the assistant to use the obsidian-change-trace skill to update the current Sandrone workspace’s Obsidian notes, verify the latest request and slice status, and record the safest next action.
High-intent search queries and answers about installing and using this skill.
To keep Obsidian notes synchronized with Sandrone tracking, the skill maintains change-trace notes by updating request indexes, slice notes, and parent-to-slice graph links with YAML metadata.
To resume a partially completed Sandrone loop, the skill generates safe resume instructions and recovery navigation aligned with immutable review artifacts and active change package indexes.
Yes, the skill works with Obsidian YAML metadata to record PR delivery status, track blockers, and summarize recovery steps without duplicating large artifacts.
The best way to track Sandrone review summaries is to use the skill to concisely summarize review states and blockers directly within Obsidian change-trace notes.
You need change-trace notes for Sandrone workspaces when a request is blocked, a PR needs reconciliation, or a new session must continue work with minimal context loss.
cpp-for-everythingDefine and validate Obsidian Base (.base) YAML files for database-like note views.
Tigha66Automate Obsidian vault navigation, note creation, and link updates via obsidian-cli.
JunHyuk-KangGenerate developer implementation instructions from planning documents and design specifications.
GenEducationMerge a pull request, wait for CI and deployment, and verify production health with canary checks.
