feat: add a subagent frame

agentlite/examples/skills/code-reviewer/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: code-reviewer
+description: Review code for bugs, style issues, security vulnerabilities, and best practices. Use when the user asks to review, check, or audit code.
+type: standard
+---
+
+# Code Reviewer
+
+A comprehensive code review skill that checks for common issues and provides actionable feedback.
+
+## Review Checklist
+
+### 1. Correctness
+- Check for logical errors
+- Verify edge cases are handled
+- Look for off-by-one errors
+- Check null/None handling
+- Verify error handling paths
+
+### 2. Style & Readability
+- Naming conventions (clear, descriptive names)
+- Code organization and structure
+- Comments where needed (not obvious code)
+- Consistent formatting
+- Function/class length
+
+### 3. Performance
+- Inefficient algorithms (O(n²) when O(n) possible)
+- Unnecessary object creation
+- Memory leaks
+- Redundant operations
+
+### 4. Security
+- SQL injection vulnerabilities
+- XSS vulnerabilities (for web code)
+- Hardcoded secrets/passwords
+- Unsafe deserialization
+- Path traversal risks
+
+### 5. Best Practices
+- DRY principle (Don't Repeat Yourself)
+- SOLID principles
+- Proper use of language features
+- Test coverage considerations
+
+## Output Format
+
+Provide your review in this structure:
+
+```
+## Summary
+Brief overall assessment
+
+## Critical Issues
+- Issue 1: Description and fix
+- Issue 2: Description and fix
+
+## Warnings
+- Warning 1: Description and suggestion
+
+## Suggestions
+- Suggestion 1: How to improve
+
+## Positive Notes
+- What's done well
+```
+
+Be constructive and specific. Include code examples for suggested fixes.

agentlite/examples/skills/release-process/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: release-process
+description: Execute the release workflow including version checks, changelog updates, and PR creation. Use when the user wants to create a new release or version.
+type: flow
+---
+
+# Release Process
+
+Follow this structured workflow to create a new release.
+
+## Flow
+
+```mermaid
+flowchart TD
+    BEGIN(( )) --> CHECK[Check for uncommitted changes]
+    CHECK --> CHANGES{Changes?}
+    CHANGES -->|Yes| COMMIT[Commit or stash changes]
+    CHANGES -->|No| VERSION{Version type?}
+    COMMIT --> VERSION
+    VERSION -->|Patch| UPDATE_PATCH[Update patch version]
+    VERSION -->|Minor| UPDATE_MINOR[Update minor version]
+    VERSION -->|Major| UPDATE_MAJOR[Update major version]
+    UPDATE_PATCH --> CHANGELOG[Update CHANGELOG.md]
+    UPDATE_MINOR --> CHANGELOG
+    UPDATE_MAJOR --> CHANGELOG
+    CHANGELOG --> BRANCH[Create release branch]
+    BRANCH --> PR[Create Pull Request]
+    PR --> END(( ))
+```
+
+## Node Details
+
+### Check for uncommitted changes
+Run `git status` and check if there are any uncommitted changes.
+
+### Commit or stash changes
+Ask the user whether to commit the changes or stash them for later.
+
+### Version type
+Ask the user what type of release this is:
+- **Patch**: Bug fixes (0.0.X)
+- **Minor**: New features, backward compatible (0.X.0)
+- **Major**: Breaking changes (X.0.0)
+
+### Update version
+Update the version number in:
+- `pyproject.toml` or `package.json`
+- Any other version files
+
+### Update CHANGELOG
+Add a new section to CHANGELOG.md with:
+- Version number and date
+- List of changes
+- Breaking changes (if any)
+- Migration notes (if needed)
+
+### Create release branch
+Create a new branch: `release/vX.Y.Z`
+
+### Create Pull Request
+Open a PR with:
+- Title: "Release vX.Y.Z"
+- Description summarizing the changes