For vibe coders
A Vibe Coding Profile (VCP) is your AI-assisted engineering persona—revealed through patterns in your commit history. We surface signals from your git history to shine a light on how you build with AI, what feels like you, what feels new, and how your workflow is evolving.
The term “vibe coding” can be polarizing, but it captures the cultural moment around AI-shaped development. We personally prefer “AI Assisted Engineering” because it’s more explicit about the role of AI. This is a playful side project, so we keep it light and approachable for non-technical folks.
Personas are an interpretation layer based on observable commit signals. They can shift as your repos and your AI habits evolve.
Fetch commit metadata
We sample up to 300 commits across your repo's lifetime (timestamps, sizes, file paths). No code content.
Filter automation noise
Bots like Dependabot or release workflows are filtered out so the signal reflects your work.
Compute metrics + axes
25+ metrics roll up into six Vibe Axes (planning, guardrails, rhythm, surface area, and more).
Detect persona + insights
We map your axes to a persona and generate streaks, timing, and workflow highlights.
Optional LLM narrative
If you opt in, we summarize patterns using metadata only—never code or message content.
Create Repo VCP
Each repo gets its own Repo VCP—a snapshot of your vibe coding style for that project.
Aggregate into Unified VCP
Multiple Repo VCPs roll into your Unified VCP, weighted by commit volume across all repos.
You may see one of these (or another persona). These are lenses on your AI-assisted engineering (vibe-coding) style. Observations, not labels.
Spec-Driven Architect
Plans thoroughly before shipping changes; constraints show up early and often.
Test-First Validator
Leans on tests as a contract; prefers safety nets before big changes.
Vibe Prototyper
Moves fast by experimenting; iterates in bursts and learns by doing.
Agent Orchestrator
Coordinates tools and assistants; breaks work into structured moves.