context-refresh

Patches patchable frontmatter fields in a project's context.md after sessions.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill context-refresh-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-refresh
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/context-refresh
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill context-refresh-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project context files drift out of date after brainstorms, ADR writing, or phase milestones, forcing agents to read stale or bloated orientation documents at session start. This Skill updates only the five patchable frontmatter fields of context.md while leaving the human-owned stable body untouched. ## Core Features & Use Cases - Scoped frontmatter patching: Updates only phase, focus, blocked_by, recent_adrs, and last_updated via Hive vault_patch, never rewriting the stable body. - Session delta extraction: Derives changes from the work actually done in the session, leaving fields unchanged when there is no signal. - Automatic and manual triggers: Runs on /context-refresh, "refresh project context", or automatically from /handoff when an ADR was written or a phase milestone closed. - Use Case: After closing a phase milestone and writing an ADR in a session, run the Skill to bump the project's phase, prepend the new ADR slug to recent_adrs, and refresh last_updated while keeping the file under 400 tokens for cheap agent orientation. ## Quick Start Ask the agent to refresh the project context for the current repository after this session's ADR and milestone work.

Frequently Asked Questions about context-refresh

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

FAQPage Schema
How do I update a project context.md file after a work session?

Run /context-refresh with an optional project name, or say "refresh project context". The Skill extracts session deltas and patches only the frontmatter fields phase, focus, blocked_by, recent_adrs, and last_updated.

What fields does context-refresh modify in context.md?

It patches only five frontmatter keys: phase, focus, blocked_by, recent_adrs, and last_updated. The stable body below the frontmatter, including vision and stack sections, is never rewritten by this Skill.

Can context-refresh run without the Obsidian GUI?

Yes, it patches files through Hive vault_patch, so it works headlessly and across agents. Vault edits auto-commit to master without requiring a branch or pull request.

When should I not use context-refresh?

Do not run it for backlog or task state changes, since those live in the GitHub Project bitácora, not in context.md. It is also skipped when a session produced no phase, focus, blocker, or ADR signals.

What happens if context.md has no patchable frontmatter?

The Skill stops and offers to migrate the legacy file to the project-context template first. It refuses to patch pre-HARNESS-006 files that lack the patchable frontmatter block.