devskill 2.0.7 → 2.0.8

package/skills/gen-specs-as-issues/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/gen-specs-as-issues/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: gen-specs-as-issues
+description: 'This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.'
+---
+
+# Product Manager Assistant: Feature Identification and Specification
+
+This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
+
+## 1. Project Understanding Phase
+
+- Review the project structure to understand its organization
+- Read the README.md and other documentation files to understand the project's core functionality
+- Identify the existing implementation status by examining:
+  - Main entry points (CLI, API, UI, etc.)
+  - Core modules and their functionality
+  - Tests to understand expected behavior
+  - Any placeholder implementations
+
+**Guiding Questions:**
+- What is the primary purpose of this project?
+- What user problems does it solve?
+- What patterns exist in the current implementation?
+- Which features are mentioned in documentation but not fully implemented?
+
+## 2. Gap Analysis Phase
+
+- Compare the documented capabilities ONLY against the actual implementation
+- Identify "placeholder" code that lacks real functionality
+- Look for features mentioned in documentation but missing robust implementation
+- Consider the user journey and identify broken or missing steps
+- Focus on core functionality first (not nice-to-have features)
+
+**Output Creation:**
+- Create a list of potential missing features (5-7 items)
+- For each feature, note:
+  - Current implementation status
+  - References in documentation
+  - Impact on user experience if missing
+
+## 3. Prioritization Phase
+
+- Apply a score to each identified gap:
+
+**Scoring Matrix (1-5 scale):**
+- User Impact: How many users benefit?
+- Strategic Alignment: Fits core mission?
+- Implementation Feasibility: Technical complexity?
+- Resource Requirements: Development effort needed?
+- Risk Level: Potential negative impacts?
+
+**Priority = (User Impact × Strategic Alignment) / (Implementation Effort × Risk Level)**
+
+**Output Creation:**
+- Present the top 3 highest-priority missing features based on the scoring
+- For each, provide:
+  - Feature name
+  - Current status
+  - Impact if not implemented
+  - Dependencies on other features
+
+## 4. Specification Development Phase
+
+- For each prioritized feature, develop a detailed but practical specification:
+  - Begin with the philosophical approach: simplicity over complexity
+  - Focus on MVP functionality first
+  - Consider the developer experience
+  - Keep the specification implementation-friendly
+
+**For Each Feature Specification:**
+1. **Overview & Scope**
+   - What problem does it solve?
+   - What's included and what's explicitly excluded?
+
+2. **Technical Requirements**
+   - Core functionality needed
+   - User-facing interfaces (API, UI, CLI, etc.)
+   - Integration points with existing code
+
+3. **Implementation Plan**
+   - Key modules/files to create or modify
+   - Simple code examples showing the approach
+   - Clear data structures and interfaces
+
+4. **Acceptance Criteria**
+   - How will we know when it's done?
+   - What specific functionality must work?
+   - What tests should pass?
+
+## 5. GitHub Issue Creation Phase
+
+- For each specification, create a GitHub issue:
+  - Clear, descriptive title
+  - Comprehensive specification in the body
+  - Appropriate labels (enhancement, high-priority, etc.)
+  - Explicitly mention MVP philosophy where relevant
+
+**Issue Template Structure:**
+
+# [Feature Name]
+
+## Overview
+[Brief description of the feature and its purpose]
+
+## Scope
+[What's included and what's explicitly excluded]
+
+## Technical Requirements
+[Specific technical needs and constraints]
+
+## Implementation Plan
+[Step-by-step approach with simple code examples]
+
+## Acceptance Criteria
+[Clear list of requirements to consider the feature complete]
+
+## Priority
+[Justification for prioritization]
+
+## Dependencies
+- **Blocks:** [List of issues blocked by this one]
+- **Blocked by:** [List of issues this one depends on]
+
+## Implementation Size
+- **Estimated effort:** [Small/Medium/Large]
+- **Sub-issues:** [Links to sub-issues if this is a parent issue]
+
+
+## 5.5 Work Distribution Optimization
+
+- **Independence Analysis**
+  - Review each specification to identify truly independent components
+  - Refactor specifications to maximize independent work streams
+  - Create clear boundaries between interdependent components
+
+- **Dependency Mapping**
+  - For features with unavoidable dependencies, establish clear issue hierarchies
+  - Create parent issues for the overall feature with sub-issues for components
+  - Explicitly document "blocked by" and "blocks" relationships
+
+- **Workload Balancing**
+  - Break down large specifications into smaller, manageable sub-issues
+  - Ensure each sub-issue represents 1-3 days of development work
+  - Include sub-issue specific acceptance criteria
+
+**Implementation Guidelines:**
+- Use GitHub issue linking syntax to create explicit relationships
+- Add labels to indicate dependency status (e.g., "blocked", "prerequisite")
+- Include estimated complexity/effort for each issue to aid sprint planning
+
+## 6. Final Review Phase
+
+- Summarize all created specifications
+- Highlight implementation dependencies between features
+- Suggest a logical implementation order
+- Note any potential challenges or considerations
+
+Remember throughout this process:
+- Favor simplicity over complexity
+- Start with minimal viable implementations that work
+- Focus on developer experience
+- Build a foundation that can be extended later
+- Consider the open-source community and contribution model
+
+This workflow embodiment of our approach should help maintain consistency in how features are specified and prioritized, ensuring that software projects evolve in a thoughtful, user-centered way.

package/skills/gen-specs-as-issues/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/gen-specs-as-issues`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/generate-custom-instructions-from-codebase/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/generate-custom-instructions-from-codebase/SKILL.md

@@ -0,0 +1,240 @@
+---
+name: generate-custom-instructions-from-codebase
+description: 'Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.'
+---
+
+# Migration and Code Evolution Instructions Generator
+
+## Configuration Variables
+
+```
+${MIGRATION_TYPE="Framework Version|Architecture Refactoring|Technology Migration|Dependencies Update|Pattern Changes"}
+<!-- Type of migration or evolution -->
+
+${SOURCE_REFERENCE="branch|commit|tag"}
+<!-- Source reference point (before state) -->
+
+${TARGET_REFERENCE="branch|commit|tag"}  
+<!-- Target reference point (after state) -->
+
+${ANALYSIS_SCOPE="Entire project|Specific folder|Modified files only"}
+<!-- Scope of analysis -->
+
+${CHANGE_FOCUS="Breaking Changes|New Conventions|Obsolete Patterns|API Changes|Configuration"}
+<!-- Main aspect of changes -->
+
+${AUTOMATION_LEVEL="Conservative|Balanced|Aggressive"}
+<!-- Level of automation for Copilot suggestions -->
+
+${GENERATE_EXAMPLES="true|false"}
+<!-- Include transformation examples -->
+
+${VALIDATION_REQUIRED="true|false"}
+<!-- Require validation before application -->
+```
+
+## Generated Prompt
+
+```
+"Analyze code evolution between two project states to generate precise migration instructions for GitHub Copilot. These instructions will guide Copilot to automatically apply the same transformation patterns during future modifications. Follow this methodology:
+
+### Phase 1: Comparative State Analysis
+
+#### Structural Changes Detection
+- Compare folder structure between ${SOURCE_REFERENCE} and ${TARGET_REFERENCE}
+- Identify moved, renamed, or deleted files
+- Analyze changes in configuration files
+- Document new dependencies and removed ones
+
+#### Code Transformation Analysis
+${MIGRATION_TYPE == "Framework Version" ? 
+  "- Identify API changes between framework versions
+   - Analyze new features being used
+   - Document obsolete methods/properties
+   - Note syntax or convention changes" : ""}
+
+${MIGRATION_TYPE == "Architecture Refactoring" ? 
+  "- Analyze architectural pattern changes
+   - Identify new abstractions introduced
+   - Document responsibility reorganization
+   - Note changes in data flows" : ""}
+
+${MIGRATION_TYPE == "Technology Migration" ? 
+  "- Analyze replacement of one technology with another
+   - Identify functional equivalences
+   - Document API and syntax changes
+   - Note new dependencies and configurations" : ""}
+
+#### Transformation Pattern Extraction
+- Identify repetitive transformations applied
+- Analyze conversion rules from old to new format
+- Document exceptions and special cases
+- Create before/after correspondence matrix
+
+### Phase 2: Migration Instructions Generation
+
+Create a `.github/copilot-migration-instructions.md` file with this structure:
+
+\`\`\`markdown
+# GitHub Copilot Migration Instructions
+
+## Migration Context
+- **Type**: ${MIGRATION_TYPE}
+- **From**: ${SOURCE_REFERENCE} 
+- **To**: ${TARGET_REFERENCE}
+- **Date**: [GENERATION_DATE]
+- **Scope**: ${ANALYSIS_SCOPE}
+
+## Automatic Transformation Rules
+
+### 1. Mandatory Transformations
+${AUTOMATION_LEVEL != "Conservative" ? 
+  "[AUTOMATIC_TRANSFORMATION_RULES]
+   - **Old Pattern**: [OLD_CODE]
+   - **New Pattern**: [NEW_CODE]
+   - **Trigger**: When to detect this pattern
+   - **Action**: Transformation to apply automatically" : ""}
+
+### 2. Transformations with Validation
+${VALIDATION_REQUIRED == "true" ? 
+  "[TRANSFORMATIONS_WITH_VALIDATION]
+   - **Detected Pattern**: [DESCRIPTION]
+   - **Suggested Transformation**: [NEW_APPROACH]
+   - **Required Validation**: [VALIDATION_CRITERIA]
+   - **Alternatives**: [ALTERNATIVE_OPTIONS]" : ""}
+
+### 3. API Correspondences
+${CHANGE_FOCUS == "API Changes" || MIGRATION_TYPE == "Framework Version" ? 
+  "[API_CORRESPONDENCE_TABLE]
+   | Old API   | New API   | Notes     | Example        |
+   | --------- | --------- | --------- | -------------- |
+   | [OLD_API] | [NEW_API] | [CHANGES] | [CODE_EXAMPLE] | " : ""} |
+
+### 4. New Patterns to Adopt
+[DETECTED_EMERGING_PATTERNS]
+- **Pattern**: [PATTERN_NAME]
+- **Usage**: [WHEN_TO_USE] 
+- **Implementation**: [HOW_TO_IMPLEMENT]
+- **Benefits**: [ADVANTAGES]
+
+### 5. Obsolete Patterns to Avoid
+[DETECTED_OBSOLETE_PATTERNS]
+- **Obsolete Pattern**: [OLD_PATTERN]
+- **Why Avoid**: [REASONS]
+- **Alternative**: [NEW_PATTERN]
+- **Migration**: [CONVERSION_STEPS]
+
+## File Type Specific Instructions
+
+${GENERATE_EXAMPLES == "true" ? 
+  "### Configuration Files
+   [CONFIG_TRANSFORMATION_EXAMPLES]
+   
+   ### Main Source Files
+   [SOURCE_TRANSFORMATION_EXAMPLES]
+   
+   ### Test Files
+   [TEST_TRANSFORMATION_EXAMPLES]" : ""}
+
+## Validation and Security
+
+### Automatic Control Points
+- Verifications to perform after each transformation
+- Tests to run to validate changes
+- Performance metrics to monitor
+- Compatibility checks to perform
+
+### Manual Escalation
+Situations requiring human intervention:
+- [COMPLEX_CASES_LIST]
+- [ARCHITECTURAL_DECISIONS]
+- [BUSINESS_IMPACTS]
+
+## Migration Monitoring
+
+### Tracking Metrics
+- Percentage of code automatically migrated
+- Number of manual validations required
+- Error rate of automatic transformations
+- Average migration time per file
+
+### Error Reporting
+How to report incorrect transformations to Copilot:
+- Feedback patterns to improve rules
+- Exceptions to document
+- Adjustments to make to instructions
+
+\`\`\`
+
+### Phase 3: Contextual Examples Generation
+
+${GENERATE_EXAMPLES == "true" ? 
+  "#### Transformation Examples
+   For each identified pattern, generate:
+   
+   \`\`\`
+   // BEFORE (${SOURCE_REFERENCE})
+   [OLD_CODE_EXAMPLE]
+   
+   // AFTER (${TARGET_REFERENCE}) 
+   [NEW_CODE_EXAMPLE]
+   
+   // COPILOT INSTRUCTIONS
+   When you see this pattern [TRIGGER], transform it to [NEW_PATTERN] following these steps: [STEPS]
+   \`\`\`" : ""}
+
+### Phase 4: Validation and Optimization
+
+#### Instructions Testing
+- Apply instructions on test code
+- Verify transformation consistency
+- Adjust rules based on results
+- Document exceptions and edge cases
+
+#### Iterative Optimization  
+${AUTOMATION_LEVEL == "Aggressive" ? 
+  "- Refine rules to maximize automation
+   - Reduce false positives in detection
+   - Improve transformation accuracy
+   - Document lessons learned" : ""}
+
+### Final Result
+
+Migration instructions that enable GitHub Copilot to:
+1. **Automatically apply** the same transformations during future modifications
+2. **Maintain consistency** with newly adopted conventions  
+3. **Avoid obsolete patterns** by automatically proposing alternatives
+4. **Accelerate future migrations** by capitalizing on acquired experience
+5. **Reduce errors** by automating repetitive transformations
+
+These instructions transform Copilot into an intelligent migration assistant, capable of reproducing your technology evolution decisions consistently and reliably.
+"
+```
+
+## Typical Use Cases
+
+### Framework Version Migration
+Perfect for documenting the transition from Angular 14 to Angular 17, React Class Components to Hooks, or .NET Framework to .NET Core. Automatically identifies breaking changes and generates corresponding transformation rules.
+
+### Technology Stack Evolution  
+Essential when replacing a technology entirely: jQuery to React, REST to GraphQL, SQL to NoSQL. Creates a comprehensive migration guide with pattern mappings.
+
+### Architecture Refactoring
+Ideal for large refactorings like Monolith to Microservices, MVC to Clean Architecture, or Component to Composable architecture. Preserves architectural knowledge for future similar transformations.
+
+### Design Pattern Modernization
+Useful for adopting new patterns: Repository Pattern, Dependency Injection, Observer to Reactive Programming. Documents the rationale and implementation differences.
+
+## Unique Benefits
+
+### 🧠 **Artificial Intelligence Enhancement**
+Unlike traditional migration documentation, these instructions "train" GitHub Copilot to reproduce your technology evolution decisions automatically during future code modifications.
+
+### 🔄 **Knowledge Capitalization**  
+Transforms specific project experience into reusable rules, avoiding the loss of migration expertise and accelerating future similar transformations.
+
+### 🎯 **Context-Aware Precision**
+Instead of generic advice, generates instructions tailored to your specific codebase, with real before/after examples from your project evolution.
+
+### ⚡ **Automated Consistency**
+Ensures that new code additions automatically follow the new conventions, preventing architectural regression and maintaining code evolution coherence.

package/skills/generate-custom-instructions-from-codebase/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/generate-custom-instructions-from-codebase`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/geofeed-tuner/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.