lightforgelabsstudio/evolve
skills/evolve/SKILL.md
Turn a repeated failure pattern into a system improvement. Outputs a concrete proposal for constraints, docs, or automation.
tools
Updated May 7, 2026
$ install --global
skillsauthnpx skillsauth add lightforgelabsstudio/aide evolveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:54 AM161.0s1 file scanned
SKILL.md
- name:
- evolve
- description:
- Turn a repeated failure pattern into a system improvement. Outputs a concrete proposal for constraints, docs, or automation.
Evolve
Convert repeated mistakes into rules or automation. Requires 2+ occurrences with evidence.
Inputs
Ask the user for:
- What happened (describe the failure)
- How many times (must be 2+ across sessions or PRs)
- Evidence (PR/issue links or excerpts)
- Where it should have been caught (tooling, docs, invariant)
Decision hierarchy (smallest effective change)
- Automate — Can tooling enforce it (lint rule, CI check, pre-commit hook)? If yes, propose automation first.
- Tier 1 constraint — Applies to all code, critical to enforce? Add to AGENTS.md invariants.
- Tier 2 guidance — System-specific, helpful but not critical? Add to the relevant doc in
docs/. - Reference only — Best practice but not enforceable? Add as a comment or reference doc.
Output format
## System Evolution Proposal
### Failure Pattern
What: <description>
Frequency: <X> times across <Y> PRs/sessions
Evidence: <links or excerpts>
### Decision: AUTOMATION | TIER 1 | TIER 2 | REFERENCE
Rationale: <1-2 sentences>
### Proposed Change
Location: <exact file path + section>
Proposed addition:
<exact text to add — use positive constraints>
### Implementation Steps
1. <what to modify>
2. <validation needed>
3. <PR creation>
Notes
- Use positive language ("Do X", not "Don't do Y").
- Do not modify files until the user approves the proposal.
- Prefer automation when possible — enforced beats documented.
Related Skills
lightforgelabsstudio/sanity-check
testing
VerifiedTrustedCommunity
Skeptical gap analysis for issues, ADRs, plans, and docs. Use when the user wants a second-pass check for missing decisions, contradictions, edge cases, hidden dependencies, scope drift, or readiness before implementation.
SKILL.mdUpdated May 11, 2026
lightforgelabsstudio/sync
tools
VerifiedTrustedCommunity
Sync branch with remote and confirm a clean end-of-session state.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/skill-author
testing
VerifiedTrustedCommunity
Create or update an AIDE skill in .aide/skills with valid frontmatter and a concise workflow.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/scope
tools
VerifiedTrustedCommunity
Decompose an accepted ADR into GitHub issues using the issue-creator tool.
SKILL.mdUpdated May 7, 2026