Skip to content

Vinix24/vnx-orchestration / skills/python-optimizer

python-optimizer

Verified

Python code performance optimization specialist

FileKindSize
SKILL.mdskill md6.1 KB
references/_MAPPING.mdmarkdown335 B
template.mdmarkdown1.7 KB

template.md

View on GitHub
# Python Optimizer Report Template

## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`

## Filename Format
`{timestamp}-{track}-optimization-{title}.md`

Example: `20260202-143000-A-optimization-memory-reduction.md`

## Report Structure

### Summary
Brief overview of optimization work completed (2-3 sentences)

### Tags (Required)
- [tag1, tag2, tag3]  # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.

### Performance Baseline
- Memory usage before optimization
- Execution time before optimization
- Profiling methodology used

### Optimizations Applied
- Code changes made with rationale
- Algorithm improvements
- Memory reduction techniques
- Async/concurrency improvements

### Results
- Memory usage after (with % reduction)
- Execution time after (with speedup factor)
- Before/after benchmark comparison

### Evidence
- Profiling output (cProfile, memory_profiler)
- Benchmark results
- Code snippets showing changes
- Test output confirming correctness

### Open Items
<!-- List any unfinished work, blockers, or issues discovered -->
<!-- Format: - [ ] [severity] Title (optional details) -->
<!-- Severities: [blocker], [warn], [info] -->
<!-- Leave empty if all work completed -->

### Recommendations
- Further optimization opportunities
- Trade-offs to consider
- Monitoring suggestions for regression detection

### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []

## Quality Standards
- 30%+ memory reduction target
- 2x+ speed improvement goal
- Maintain code readability
- Include benchmark results
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall