From majestic-engineer
Generates documentary-style narrative of git repository development history from commits, tags, and contributors. Outputs to STORY.md with configurable detail, date, and commit limits.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineer[--output PATH] [--detail minimal|standard|comprehensive] [--since DATE] [--commits N]git/Transform git history into an engaging documentary narrative.
## Context
- Default branch: !`git remote show origin | grep 'HEAD branch' | awk '{print $NF}'`
- Repository root: !`git rev-parse --show-toplevel 2>/dev/null`
- Total commits: !`git rev-list --count HEAD 2>/dev/null`
- First commit: !`git log --reverse --format="%H|%ai|%an|%s" 2>/dev/null | head -1`
## Arguments
| Option | Format | Default | Description |
|--------|--------|---------|-------------|
| `--output` | PATH | STORY.md | Output file |
| `--detail` | minimal\|standard\|comprehensive | standard | Detail level |
| `--.../changelogGenerate structured changelog from recent git commits, grouped by date and categorized by type (features, fixes, etc.) in markdown format.
/historyAnalyzes commit history of a GitHub/GitLab repo to discover debugging patterns, workflows, refactoring strategies, and improvements, suggesting applications to the current project.
/code-historyAnalyzes git history and code evolution patterns for project, files, authors, PRs, hotspots, or co-changes, producing succinct executive markdown report.
/retroGenerates git-based engineering retrospectives with summary metrics, contributor breakdowns, commit types, hotspots, and trends over a time window (default 7d).
/SKILLAnalyzes git commit history for hotspots, temporal coupling, recent contributors, and risk assessment. Generates report saved to .sourceatlas/history.md. Supports optional path/scope.
Share bugs, ideas, or general feedback.
Transform git history into an engaging documentary narrative.
git remote show origin | grep 'HEAD branch' | awk '{print $NF}'git rev-parse --show-toplevel 2>/dev/nullgit rev-list --count HEAD 2>/dev/nullgit log --reverse --format="%H|%ai|%an|%s" 2>/dev/null | head -1| Option | Format | Default | Description |
|---|---|---|---|
--output | PATH | STORY.md | Output file |
--detail | minimal|standard|comprehensive | standard | Detail level |
--since | YYYY-MM-DD | (all) | Analyze after date |
--commits | N | (all) | Limit to N commits |
git rev-parse --git-dir)For large repos:
Always include:
Sample size by detail:
minimal: 20 additionalstandard: 50 additionalcomprehensive: 100 additional# Project name, age, tags, top contributors, monthly distribution
basename "$(git rev-parse --show-toplevel)"
git log --reverse --format="%ai" | head -1
git tag -l --format='%(creatordate:short)|%(refname:short)' | sort
git shortlog -sn --no-merges | head -10
Invoke git-researcher agent:
Task (majestic-engineer:research:git-researcher):
Analyze evolution: milestones, contributor growth, architecture changes,
development patterns, turning points.
Invoke code-story skill which will guide you to find and read the appropriate template:
Skill(skill="code-story")
Follow the skill's instructions to load the template matching the detail level.
📚 Code Story Generated
**Output:** [file_path]
**Detail Level:** [minimal|standard|comprehensive]
**Commits Analyzed:** [count]
**Contributors Featured:** [count]
The story is ready: [file_path]
| Scenario | Response |
|---|---|
| Not a git repo | "Error: Not a git repository" |
| Empty repo | "Error: Empty repository" |
| Single commit | Generate "genesis only" minimal story |
| No tags | Note: "No formal releases yet" |