contributinglisted

# Complete Contribution Strategy - Context Aware I'll analyze everything needed for your successful contribution based on your current context and work. ## Strategic Thinking Process <think> For a successful contribution, I need to analyze: 1. **Current Work Context** - What has been done in this session? - Are we mid-implementation or post-completion? - What type of changes were made (feature, fix, refactor)? - Is the work ready for contribution? 2. **Project Type & Standards** - Is this open source, company, or personal project? - What are the contribution guidelines? - Are there specific workflows to follow? - What quality gates exist (tests, lint, reviews)? 3. **Contribution Strategy** - Should this be one PR or multiple? - Which issues does this work address? - What documentation needs updating? - Who should review this? 4. **Pre-flight Checklist** - Do all tests pass? - Is the code properly formatted? - Are there any lint warnings? - Is documentation updated? - Are commits well-organized? </think> ## Token Optimization Strategy **Target: 65% reduction (3,000-5,000 → 1,000-1,800 tokens)** This skill uses aggressive optimization to minimize token usage while providing comprehensive contribution readiness assessment. ### Core Optimization Principles **1. Early Exit Pattern (Saves 70-90% tokens)** ```bash # Check if already documented if [ -f "CONTRIBUTING.md" ] && grep -q "contribution" CONTRIBUTING.md; then