skills.rest
laitim2001
laitim2001COMMUNITY
Explore all skills by this author →
GitHub

v9-sync

Detect source-code changes and update V9 analysis files via git diffs.

Updated Oct 29, 2025
Search Tags:#automation#documentation#sprint-tracking#codebase-analysis#git-diff#v9-sync#semantic-sync
One-click install
npx skills add https://github.com/laitim2001/ai-semantic-kernel-framework-project --skill v9-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: v9-sync
Source: https://github.com/laitim2001/ai-semantic-kernel-framework-project/tree/main/.claude/skills/v9-sync
Command: npx skills add https://github.com/laitim2001/ai-semantic-kernel-framework-project --skill v9-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects source-code changes since the last V9 sync and semantically updates the corresponding V9 analysis files.

Core Features & Use Cases

  • Supports full sync, report-only, targeted file sync (e.g., --file <layer-name>), and stats-only updates.
  • Maps changed directories to V9 files and updates analysis content with evidence-based reasoning.
  • Designed for backend and frontend codebases within the V9 analysis workflow to maintain synchronization across sprint cycles.

Quick Start

Run /v9-sync to perform a full synchronization of V9 analysis with the latest code changes.

Frequently Asked Questions about v9-sync

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

FAQPage Schema
How do I automatically update documentation after semantic codebase analysis changes?▼

To automatically update documentation after semantic codebase analysis changes, run a sync command that computes git diffs across source directories and updates the corresponding analysis files with evidence-backed reasoning.

Can I synchronize analysis files for a specific frontend or backend layer instead of the entire codebase?▼

Yes, you can synchronize analysis files for a specific frontend or backend layer using targeted file sync. By specifying a layer name, the tool maps only the changed directories to their corresponding analysis files.

What is the best way to track source-code changes across sprint cycles for documentation?▼

Tracking source-code changes across sprint cycles is done by reading the previous verification state, computing git diffs across backend and frontend source folders, and semantically updating the analysis files accordingly.

Does this semantic sync tool support generating reports without modifying the full analysis content?▼

Yes, the semantic sync tool supports a report-only mode that generates analysis reports without writing the full updated content, alongside a stats-only mode for quick update metrics.

How does git diff mapping work when updating analysis files for a modified codebase?▼

Git diff mapping for updating analysis files works by detecting source-code changes since the last synchronization, mapping the changed directories to their respective analysis files, and writing updated content based on extracted evidence.

Related Skills

Explore More Software Engineering Skills→
wibus-weewibus-wee
6

frontend-guardrails

Enforce centralized SWR keys, UI settings, and form configuration guardrails in frontend code.

Community
Advanced
darsoohoodarsoohoo

recipe-design

Orchestrate codebase analysis, ADR creation, and design documentation workflows.

Community
Advanced
danilonovaisvdanilonovaisv
1

github-project-management

Coordinate GitHub issues, boards, and sprint planning across repositories.

Community
Advanced
LimaTechnologiesLimaTechnologies

docs-tracker

Track codebase changes with git diff and update documentation and changelogs.

Community
Intermediate