timeline-manager

Manage Git worktrees and branching timelines for project audits.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ojallington/boardclaude --skill timeline-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timeline-manager
Source: https://github.com/ojallington/boardclaude/tree/main/skills/timeline-manager
Command: npx skills add https://github.com/ojallington/boardclaude --skill timeline-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a clear, visual history of project development by tracking every audit, experimental branch, merge, and rollback, making strategic decisions transparent.

Core Features & Use Cases

  • Branching Timeline: Manages a Git-based branching strategy for isolated experimentation.
  • Audit Tracking: Records and visualizes audit results, forks, merges, and rollbacks.
  • Use Case: When iterating on a feature, use this Skill to fork a new branch for each experimental approach, compare their audit results, and then merge the winning approach back into the main development line.

Quick Start

Use the timeline-manager skill to fork a new branch named 'feature-x-experiment' for testing a new hypothesis.

Frequently Asked Questions about timeline-manager

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

FAQPage Schema
How do I manage parallel experimentation branches in Git for AI-driven audits?

To manage parallel experimentation in Git for AI-driven audits, this Skill uses Git worktrees to create isolated development branches, enabling you to fork experimental paths and compare audit results before merging the winning approach back into the main timeline.

What is a branching timeline for project development and how does it track rollbacks?

A branching timeline for project development tracks every audit, experimental fork, merge, and rollback using Git. It visualizes project evolution transparently, providing a clear history of strategic decisions and enabling straightforward rollbacks to previous states.

How do I fork a new Git worktree to test an experimental feature approach?

You can fork a new Git worktree to test an experimental feature by instructing the Skill to create an isolated branch, such as 'feature-x-experiment', which allows you to test a new hypothesis without impacting your main development line.

Can I compare audit results from different Git branches before merging?

Yes, you can compare audit results from different Git branches. The Skill manages isolated development worktrees and handles audit result comparison, allowing you to evaluate parallel experiments and strategically merge the winning approach.

Does this branching timeline manager work without external dependencies?

Yes, the branching timeline manager operates without external dependencies, relying solely on internal scripts and references to manage Git worktrees, visualize project state, and handle strategic merges or rollbacks.

When should I use Git worktrees for isolated development instead of standard branching?

You should use Git worktrees for isolated development when iterating on features that require parallel experimentation and transparent audit tracking. This approach prevents main branch contamination and supports clear audit result comparison before strategic merges.