project-skill-audit

To identify needed automation skills, analyze project session history and memory files to find recurring bottlenecks and manual validation steps. This evidence-based approach targets specific failure patterns to generate actionable improvement plans for developer productivity.

Prevent repository bloat by auditing rollout summaries and existing local skill definitions to distinguish between creating a new skill and updating an existing one. Skill lifecycle management ensures you only add automations justified by session history evidence.

Yes, you can use session history to find repetitive manual validation sequences. Analyzing project memory indices and rollout summaries targets recurring workflows, allowing you to encode those specific project guardrails into custom automations.

Audit project memory files by reviewing session history, memory indices, and local skill definitions to pinpoint recurring workflows and failure patterns. This data-driven analysis generates actionable improvement plans that optimize developer efficiency.

Yes, you need project memory indices, rollout summaries, and existing local skill definitions to recommend high-value refactoring skills. Access to this historical session data is required to identify recurring bottlenecks and generate actionable improvement plans.