Skip to content

Tibsfox/gsd-skill-creator / skills/gource-visualizer

gource-visualizer

Flagged

Produce animated source control visualizations using Gource. This skill handles installation of Gource and ffmpeg, detection of repository metrics, preset-based configuration, single and multi-repo log generation, ffmpeg video encoding pipeline, headless rendering for server environments, caption generation from git tags, GitHub avatar resolution, and GSD output delivery. Use this skill whenever the user wants to visualize repository history, create a code evolution video, see project timeline animations, generate Gource videos, combine multiple repos into one visualization, or produce any kind of source control visualization. Also trigger when the user mentions "Gource", "repo visualization", "code history video", "project evolution animation", or asks to "show me what we built".

Gource Visualizer

Gource is an open-source software version control visualization tool that renders repository history as an animated tree. This skill orchestrates the full pipeline from installation through rendering, producing MP4 or WebM video files, PNG thumbnails, and render summary reports. It activates when a user wants to visualize repository history, create a code evolution video, generate a Gource animation, see project timelines, or says "show me what we built."

All script paths below are relative to skills/gource-visualizer/.

Quick Start

The 80% case: a single git repository, one video output.

  1. Install dependencies (idempotent -- skips if already present):

    bash scripts/install-gource.sh
    
  2. Detect repository metrics -- captures commit count, contributors, date range as JSON:

    bash scripts/detect-repo.sh <repo-path>
    
  3. Select a preset based on user intent (default: standard):

    • "quick look" / "preview" --> quick
    • "presentation" / "demo" --> standard
    • "publication" / "YouTube" / "portfolio" --> cinematic
    • "thumbnail" / "screenshot" --> thumbnail
  4. Render the video:

    bash scripts/render-video.sh --repo <repo-path> --preset standard --output <output-dir>/video.mp4
    

    The render script auto-calculates --seconds-per-day from repository metrics and preset target duration. It auto-detects headless environments and delegates to scripts/render-headless.sh when no display is available.

  5. Deliver output to the user with a summary: video file path, duration, resolution, file size, repository metrics (commits, contributors, date range).

Decision Tree

Route user intent through this tree to select the right workflow path.

User wants a visualization
  |
  +-- Single repo in current directory?
  |   +-- Yes --> Quick Start path (above)
  |   +-- No  --> Ask which repo, or detect workspace repos
  |
  +-- Multiple repos mentioned?
  |   +-- Yes --> Multi-Repository Workflow (below)
  |
  +-- Specific time range mentioned?
  |   +-- Yes --> Add --start-date YYYY-MM-DD --stop-date YYYY-MM-DD
  |
  +-- Quality or purpose mentioned?
  |   +-- "quick look" / "preview"              --> preset: quick
  |   +-- "presentation" / "demo"               --> preset: standard
  |   +-- "publication" / "YouTube" / "portfolio" --> preset: cinematic
  |   +-- "thumbnail" / "screenshot"            --> preset: thumbnail
  |
  +-- No display / CI / server environment?
      +-- Auto-detected by render-video.sh; --headless flag added automatically

Multi-Repository Workflow

Combine multiple repositories into a single visualization with namespace prefixing and optional per-repo color coding.

  1. Collect repository paths from the user.
  2. Merge logs with color coding:
    bash scripts/merge-repos.sh --color --output combined.log <repo1> <repo2> ...
    
  3. Render the combined log:
    bash scripts/render-video.sh --repo combined.log --preset <preset> --output <output-dir>/video.mp4
    

For detailed multi-repo configuration (namespace prefixing, color palette, chronological sorting), see references/multi-repo-guide.md.

Enhancement Options

Optional enhancements to add to any render command:

  • Captions (milestone markers from git tags):

    bash scripts/generate-captions.sh <repo-path> captions.txt
    

    Then pass --caption-file captions.txt to render-video.sh.

  • Avatars (GitHub profile pictures for contributors):

    bash scripts/resolve-avatars.sh <repo-path> avatars/
    

    Then pass --avatar-dir avatars/ to render-video.sh.

  • Logo overlay: --logo path/to/logo.png

  • Title overlay: --title "Project Name"

  • Custom time range: --start-date YYYY-MM-DD --stop-date YYYY-MM-DD

  • WebM format: --format webm (VP9 codec instead of H.264)

  • Audio track: Post-process with ffmpeg to add music (see references/ffmpeg-pipeline.md).

Preset Reference

PresetResolutionFPSUse CaseTarget Duration
quick720p (1280x720)30Fast preview, iteration~30s
standard1080p (1920x1080)60Presentations, demos~3 min
cinematic1080p (1920x1080)60YouTube, portfolio, publication~4 min
thumbnail1080p (1920x1080)--Single frame capture< 10s

Preset configs are at configs/preset-<name>.conf. The render script auto-calculates --seconds-per-day to hit the target duration based on repository date range.

For preset customization and parameter details, see references/presets.md.

Reference Documents

ReferenceWhen to ReadPurpose
references/installation-guide.mdInstallation fails or platform-specific issuesDetailed platform install procedures (apt, brew, manual)
references/presets.mdUser wants to understand or customize presetsPreset breakdown, parameter tuning, config format
references/ffmpeg-pipeline.mdVideo encoding issues, format conversion, audioComplete ffmpeg recipe book for post-processing
references/multi-repo-guide.mdCombining multiple repositoriesStep-by-step multi-repo workflow with examples
references/custom-log-format.mdNon-git sources, manual log creationGource custom log format specification
references/option-reference.mdAdvanced customization beyond presetsCurated Gource option guide with examples

Troubleshooting

SymptomCauseFix
"could not initialize SDL"No display / headless environmentUse --headless flag or scripts/render-headless.sh
"Xvfb failed to start"Xvfb not installedsudo apt-get install xvfb
Black or corrupt videoffmpeg framerate mismatchEnsure ffmpeg -r matches Gource --output-framerate in preset config
No users visibleNo commits in selected date rangeWiden --start-date / --stop-date range
Very fast or slow videoAuto-timing miscalculationOverride with explicit --seconds-per-day value
"libx264 not found"ffmpeg missing H.264 codecsudo apt-get install libx264-dev or reinstall ffmpeg from package

GSD Integration

When running under a GSD workflow, output files go to the GSD output directory. The render summary includes: video path, duration, resolution, repo metrics, and contributor count.

For post-milestone visualization, read the milestone's git tag range to set --start-date and --stop-date, producing a video that covers exactly that milestone's development period.

The skill works with the gource-visualizer agent pipeline (see agents/ directory) for fully automated multi-step workflows including installation, detection, rendering, and delivery.

Script Inventory

ScriptPurpose
scripts/install-gource.shIdempotent installer for Gource, ffmpeg, Xvfb
scripts/detect-repo.shVCS detection and metrics extraction (JSON output)
scripts/generate-log.shSingle-repo Gource custom log generation
scripts/merge-repos.shMulti-repo log merge with namespacing and color
scripts/generate-captions.shGit tags to Gource caption format
scripts/resolve-avatars.shGitHub API avatar fetcher with caching
scripts/render-video.shGource-to-ffmpeg render pipeline orchestrator
scripts/render-headless.shXvfb wrapper for headless environments
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexVerifiedInstall