application-research-sync

Update repository research documents to match current code changes.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/byron1st/personal-harness --skill application-research-sync-byron1st
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: application-research-sync
Source: https://github.com/byron1st/personal-harness/tree/main/skills/application-research-sync
Command: npx skills add https://github.com/byron1st/personal-harness --skill application-research-sync-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research documents under docs/agents/research drift out of date as code evolves, leaving architecture and flow descriptions that no longer match reality. This Skill detects which research files are affected by code changes and applies targeted updates so the documentation stays accurate. ## Core Features & Use Cases - Scoped Change Detection: Sync against uncommitted changes, a commit range via git diff, or the full codebase when files have drifted gradually. - Index-Driven Selection: Reads docs/agents/research/index.md to pick only the research files whose descriptions cover the modified features, and rebuilds the index from frontmatter if it is missing. - Targeted Editing: Preserves each file's existing tone, structure, and investigative register while revising stale content, updating code snippets, and keeping index.md rows in sync with frontmatter changes. - Use Case: After implementing a feature branch, run this Skill before committing so every affected research document reflects the new flows without manual doc auditing. ## Quick Start Sync the research docs in docs/agents/research with my uncommitted changes and report which files were updated.

Frequently Asked Questions about application-research-sync

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

FAQPage Schema
How do I keep research documentation in sync with code changes?▼

Run the sync after implementation by choosing a scope: uncommitted changes via git diff HEAD, changes since a specific commit, or a full-codebase pass. The Skill reads the research index, selects affected files, and applies targeted edits to match the current code.

How does the skill decide which research files need updating?▼

It reads docs/agents/research/index.md and matches each row's Description against the changed features, flows, and modules. When in doubt it includes the file, since one unnecessary review is cheaper than leaving a document wrong.

What happens if the research index.md file is missing?▼

If index.md is missing but research files exist, the Skill rebuilds the index from their frontmatter first, then continues with the sync. If no research files exist at all, it reports that and stops.

Can I sync research docs against a specific commit range?▼

Yes, the Since commit mode runs git diff against a commit hash you provide and syncs everything changed after it. An empty diff means there is nothing to sync, and the Skill says so and stops.

When should I use full-codebase mode instead of a git diff?▼

Use full-codebase mode when research files have drifted gradually with no single change point to diff against. It compares each research file directly against the current source tree rather than relying on a diff.