skills.rest
estevanhernandez-stack-ed
estevanhernandez-stack-edCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

evolve

Analyze Vibe Test usage logs to propose SKILL edits for manual review.

Updated Apr 21, 2026
Search Tags:#self-improvement#proposals#audit-trail#evolve#friction-analysis#vibe-test
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill evolve-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolve
Source: https://github.com/estevanhernandez-stack-ed/vibe-test/tree/main/packages/vibe-test/skills/evolve
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-test --skill evolve-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables a self-reflective loop for Vibe Test to analyze friction and wins logs, propose evidence-based SKILL edits, and preserve a clear audit trail without directly modifying user projects.

Core Features & Use Cases

  • Reads friction.jsonl, wins.jsonl, and recent session logs from the last 30 days.
  • Generates proposed SKILL edits to packages/vibe-test/proposed-changes.md for manual review.
  • Ensures no automatic changes to user code and maintains an auditable paper trail via applied changes.

Quick Start

From inside the vibe-test repository, run /vibe-test:evolve to generate proposed changes for self-improvement.

Frequently Asked Questions about evolve

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

FAQPage Schema
How do I analyze session logs to propose skill improvements?▼

To propose skill improvements, you can analyze friction.jsonl, wins.jsonl, and session logs from the last 30 days to generate evidence-based edits for manual review.

What is a self-reflective loop for friction analysis in a monorepo?▼

A self-reflective loop for friction analysis identifies self-improvement opportunities by evaluating usage logs within a monorepo to propose edits while preserving a clear audit trail.

How do I ensure an auditable workflow when proposing code edits?▼

You ensure an auditable workflow for code edits by writing proposals to a dedicated file like proposed-changes.md and requiring manual review before applying any modifications.

Can I automatically apply proposed changes to user projects?▼

No, proposed changes cannot be automatically applied to user projects; the system ensures no automatic modifications and requires manual review of generated proposals.

What format do proposed skill edits get written to?▼

Proposed skill edits are written to a markdown file at packages/vibe-test/proposed-changes.md, ensuring an auditable paper trail without directly altering user code.

Related Skills

Explore More Software Engineering Skills→
zubair-trabzadazubair-trabzada
2.3k

Social Media Content Calendar & Generation

Generate a 30-day social content calendar with platform-specific posts and hashtags.

Community
Advanced
tfunk1030tfunk1030
1

commit

Plan and create user-approved git commits with documented reasoning trails.

Community
Advanced
NnnsightnnnNnnsightnnn
2

Pain Point Manager

Capture and classify pain points from conversations with priority and context.

Community
Intermediate
leeoveryleeovery
27

migrate

Apply pending migrations to sync workflow files with system design.

Community
Basic