Git Workflows and Co-change Patterns

VerifiedSafe

Analyzes 200 commits to extract commit conventions, files that change together, and iteration rhythms. Helps plan multi-file changes safely.

Sby Skills Guide Bot
DevelopmentIntermediate
9/9/2026
Claude Code
#git-history#codebase-conventions#co-change-patterns#commit-style#refactoring

Recommended for

Automated summary

This skill encodes ProAnimate's repository conventions derived from its Git history — commit formats, file co-change clusters, high-churn files and iteration rhythms — to steer multi-file changes.

Strengths

  • Gives precise, evidence-backed rules such as the 3-file rule for adding a panel (types/editor.ts, tabGroups.ts, LeftPanel.tsx), with commit evidence cited
  • Flags high-churn, revert-prone files (WhiteboardPanel.tsx, RightPanel.tsx) and advises confirming visual changes with the user before committing
  • Documents both accepted commit message styles (conventional and imperative verbs) along with their relative frequencies
  • Surfaces the recurring panel-consolidation pattern, prompting a check for whether a new panel should merge into an existing tab instead

Limitations

  • Based on only 200 commits over a three-day window (2026-03-17 to 2026-03-19), a narrow snapshot that may miss older conventions
  • Tightly bound to ProAnimate's specific paths and architecture, so not reusable on another repository as-is
  • Auto-applied and not user-invocable, giving no explicit control over when it activates
  • Covers no testing, CI/CD or backend service conventions
When to use it

Use it when planning multi-file changes in ProAnimate, such as adding or moving a panel, editing whiteboard features, or picking a commit message format.

When not to use it

Avoid it on other repositories or for work outside the analyzed areas, such as tests, continuous integration or server-side services.

Security analysis

Safe
Quality score86/100

The skill contains only descriptive guidance derived from git history: commit conventions, file co-change patterns, iteration rhythms, high-churn file lists, and architecture hotspots. It does not instruct or perform any execution, network access, file modification, or data exfiltration. No tools are declared, and the content is purely informational for planning multi-file changes.

No concerns found

How this analysis is made

Examples

Add a new left panel
Add a new 'Audio Waveform' panel to the left panel in ProAnimate, updating every file that needs to change.
Whiteboard change triage
I'm modifying the whiteboard drawing overlay — which other files should I check, and how should I split the commits?
Commit message for tab move
Write a commit message for moving the Motion AI tab into the Assets group.

name: repo-workflows description: Git-history-derived workflows, co-change patterns, and iteration rhythms for ProAnimate. Auto-applied when planning multi-file changes. version: 1.0.0 source: local-git-analysis analyzed_commits: 200 user-invocable: false

ProAnimate Repository Workflows

Patterns extracted from the last 200 commits (2026-03-17 to 2026-03-19).

Commit Conventions

Format: type(scope): description

| Type | Usage | Frequency | |------|-------|-----------| | feat | New features | ~20% of commits | | fix | Bug fixes | ~2% | | Add | New files/features (informal) | ~18% | | Fix | Bug fixes (informal) | ~18% | | Move | Reorganizing tabs/panels | ~6% | | Remove | Cleanup | ~5% | | Replace | Swapping implementations | ~4.5% | | Revert/Restore | Undoing changes | ~4% |

Scopes (when conventional): mobile, core, timeline, api, server

Note: About half of commits use conventional format (feat(scope):), the other half use imperative verbs (Add, Fix, Move). Both are acceptable.

File Co-Change Patterns

These files almost always change together. If you touch one, check the others.

Adding a Panel (3-file rule)

  1. src/types/editor.ts — add tab ID to union type
  2. src/constants/tabGroups.ts — register in TAB_GROUPS array
  3. src/components/layout/LeftPanel/LeftPanel.tsx — add lazy import + PanelContent case

Evidence: 100% of panel-addition commits touch all 3 files.

Moving/Reorganizing Tabs

  1. src/constants/tabGroups.ts — move sub-tab between groups
  2. Sometimes src/types/editor.ts — if TabGroupId changes
  3. Sometimes src/components/layout/LeftPanel/LeftPanel.tsx — if GROUP_ICONS needs update

Whiteboard Feature Changes (5-file cluster)

  1. src/components/panels/WhiteboardPanel.tsx (32 changes — most changed file)
  2. src/components/canvas/WhiteboardDrawingOverlay.tsx (21 changes)
  3. src/components/canvas/WhiteboardLayer.tsx (16 changes)
  4. src/stores/useWhiteboardStore.ts (13 changes)
  5. src/services/whiteboardAnimation.ts (13 changes)

Right Panel Properties

  • src/components/layout/RightPanel/RightPanel.tsx co-changes with any panel that has properties
  • Whiteboard properties panels (Drawing, Text, Stroke) change together

Iteration Rhythms

Revert-Heavy Areas

The whiteboard and drawing tools have a high revert rate (~10 reverts in 200 commits). This indicates:

  • UI preferences are subjective — always confirm visual changes with the user before committing
  • Keep reverts cheap — make small, atomic commits for visual/UX changes
  • Common revert patterns: draw style presets, color picker layouts, cursor icons, brush settings

Mobile Sprint Pattern

Mobile features (feat(mobile):) come in rapid sequential commits (30 commits in 1 day). Each commit is atomic:

  1. Infrastructure first (auth, stores, API client)
  2. Renderers and engines next (DynamicRenderer, TypographyRenderer)
  3. Screens last (browse, editor, projects, export)
  4. Polish/fix passes after (fix(mobile):)

Panel Consolidation Pattern

Recurring pattern of merging panels:

  • Merge Style Effects into Mixed Media panel
  • Merge Camera into Cinema Studio
  • Consolidate SVG Art, Components, Motion AI, and Animations into single Assets tab

Lesson: Before adding a new panel, check if it should merge into an existing one.

High-Churn Files (Touch With Care)

| File | Changes | Risk | |------|---------|------| | WhiteboardPanel.tsx | 32 | Highly iterated, revert-prone | | RightPanel.tsx | 32 | Many panels feed into it | | WhiteboardDrawingOverlay.tsx | 21 | Complex interaction logic | | VideoCanvas.tsx | 20 | Core rendering surface | | WhiteboardLayer.tsx | 16 | Rendering pipeline | | tabGroups.ts | 14 | Tab organization (merge conflicts) | | editor.ts (types) | 13 | Type unions grow frequently |

Architecture Hotspots

Left Panel System

  • LeftPanel.tsx renders all panels through PanelContent switch
  • Tab groups defined in tabGroups.ts drive navigation
  • Large groups (>threshold) show card grid; small groups go direct to panel
  • DrillDownHeader provides prev/next navigation within groups

Layout Hierarchy

EditorLayout
├── TopMenuBar
├── LeftPanel (collapsible, 300px)
│   ├── MainGroupHeader / DrillDownHeader
│   └── PanelContent (lazy-loaded)
├── Center (flex-1)
│   ├── VideoCanvas / BRViewport / RigEditor3DViewport
│   └── Timeline / BRTimeline / Rig3DTimeline
└── RightPanel (context-sensitive properties)

Collapse Toggle Pattern

Toggle buttons for collapsible panels must be siblings of the panel in the flex layout, never children. Placing a toggle inside an overflow-hidden collapsible container causes it to be clipped when collapsed.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-workflows-and-co-change-patterns-mttmx7nd/download' --output '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md.part' && mv '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md.part' '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md' && test -s '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/repo-workflows' && cp -R '.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd' '.claude/skills/repo-workflows'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd'

openskills read 'git-workflows-and-co-change-patterns-mttmx7nd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-workflows-and-co-change-patterns-mttmx7nd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills