devskill 2.0.6 → 2.0.8

package/skills/create-github-action-workflow-specification/SKILL.md

@@ -0,0 +1,276 @@
+---
+name: create-github-action-workflow-specification
+description: 'Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.'
+---
+
+# Create GitHub Actions Workflow Specification
+
+Create a comprehensive specification for the GitHub Actions workflow: `${input:WorkflowFile}`.
+
+This specification serves as a specification for the workflow's behavior, requirements, and constraints. It must be implementation-agnostic, focusing on **what** the workflow accomplishes rather than **how** it's implemented.
+
+## AI-Optimized Requirements
+
+- **Token Efficiency**: Use concise language without sacrificing clarity
+- **Structured Data**: Leverage tables, lists, and diagrams for dense information
+- **Semantic Clarity**: Use precise terminology consistently throughout
+- **Implementation Abstraction**: Avoid specific syntax, commands, or tool versions
+- **Maintainability**: Design for easy updates as workflow evolves
+
+## Specification Template
+
+Save as: `/spec/spec-process-cicd-[workflow-name].md`
+
+```md
+---
+title: CI/CD Workflow Specification - [Workflow Name]
+version: 1.0
+date_created: [YYYY-MM-DD]
+last_updated: [YYYY-MM-DD]
+owner: DevOps Team
+tags: [process, cicd, github-actions, automation, [domain-specific-tags]]
+---
+
+## Workflow Overview
+
+**Purpose**: [One sentence describing workflow's primary goal]
+**Trigger Events**: [List trigger conditions]
+**Target Environments**: [Environment scope]
+
+## Execution Flow Diagram
+
+```mermaid
+graph TD
+    A[Trigger Event] --> B[Job 1]
+    B --> C[Job 2]
+    C --> D[Job 3]
+    D --> E[End]
+    
+    B --> F[Parallel Job]
+    F --> D
+    
+    style A fill:#e1f5fe
+    style E fill:#e8f5e8
+```
+
+## Jobs & Dependencies
+
+| Job Name | Purpose | Dependencies | Execution Context |
+|----------|---------|--------------|-------------------|
+| job-1 | [Purpose] | [Prerequisites] | [Runner/Environment] |
+| job-2 | [Purpose] | job-1 | [Runner/Environment] |
+
+## Requirements Matrix
+
+### Functional Requirements
+| ID | Requirement | Priority | Acceptance Criteria |
+|----|-------------|----------|-------------------|
+| REQ-001 | [Requirement] | High | [Testable criteria] |
+| REQ-002 | [Requirement] | Medium | [Testable criteria] |
+
+### Security Requirements
+| ID | Requirement | Implementation Constraint |
+|----|-------------|---------------------------|
+| SEC-001 | [Security requirement] | [Constraint description] |
+
+### Performance Requirements
+| ID | Metric | Target | Measurement Method |
+|----|-------|--------|-------------------|
+| PERF-001 | [Metric] | [Target value] | [How measured] |
+
+## Input/Output Contracts
+
+### Inputs
+
+```yaml
+# Environment Variables
+ENV_VAR_1: string  # Purpose: [description]
+ENV_VAR_2: secret  # Purpose: [description]
+
+# Repository Triggers
+paths: [list of path filters]
+branches: [list of branch patterns]
+```
+
+### Outputs
+
+```yaml
+# Job Outputs
+job_1_output: string  # Description: [purpose]
+build_artifact: file  # Description: [content type]
+```
+
+### Secrets & Variables
+
+| Type | Name | Purpose | Scope |
+|------|------|---------|-------|
+| Secret | SECRET_1 | [Purpose] | Workflow |
+| Variable | VAR_1 | [Purpose] | Repository |
+
+## Execution Constraints
+
+### Runtime Constraints
+
+- **Timeout**: [Maximum execution time]
+- **Concurrency**: [Parallel execution limits]
+- **Resource Limits**: [Memory/CPU constraints]
+
+### Environmental Constraints
+
+- **Runner Requirements**: [OS/hardware needs]
+- **Network Access**: [External connectivity needs]
+- **Permissions**: [Required access levels]
+
+## Error Handling Strategy
+
+| Error Type | Response | Recovery Action |
+|------------|----------|-----------------|
+| Build Failure | [Response] | [Recovery steps] |
+| Test Failure | [Response] | [Recovery steps] |
+| Deployment Failure | [Response] | [Recovery steps] |
+
+## Quality Gates
+
+### Gate Definitions
+
+| Gate | Criteria | Bypass Conditions |
+|------|----------|-------------------|
+| Code Quality | [Standards] | [When allowed] |
+| Security Scan | [Thresholds] | [When allowed] |
+| Test Coverage | [Percentage] | [When allowed] |
+
+## Monitoring & Observability
+
+### Key Metrics
+
+- **Success Rate**: [Target percentage]
+- **Execution Time**: [Target duration]
+- **Resource Usage**: [Monitoring approach]
+
+### Alerting
+
+| Condition | Severity | Notification Target |
+|-----------|----------|-------------------|
+| [Condition] | [Level] | [Who/Where] |
+
+## Integration Points
+
+### External Systems
+
+| System | Integration Type | Data Exchange | SLA Requirements |
+|--------|------------------|---------------|------------------|
+| [System] | [Type] | [Data format] | [Requirements] |
+
+### Dependent Workflows
+
+| Workflow | Relationship | Trigger Mechanism |
+|----------|--------------|-------------------|
+| [Workflow] | [Type] | [How triggered] |
+
+## Compliance & Governance
+
+### Audit Requirements
+
+- **Execution Logs**: [Retention policy]
+- **Approval Gates**: [Required approvals]
+- **Change Control**: [Update process]
+
+### Security Controls
+
+- **Access Control**: [Permission model]
+- **Secret Management**: [Rotation policy]
+- **Vulnerability Scanning**: [Scan frequency]
+
+## Edge Cases & Exceptions
+
+### Scenario Matrix
+
+| Scenario | Expected Behavior | Validation Method |
+|----------|-------------------|-------------------|
+| [Edge case] | [Behavior] | [How to verify] |
+
+## Validation Criteria
+
+### Workflow Validation
+
+- **VLD-001**: [Validation rule]
+- **VLD-002**: [Validation rule]
+
+### Performance Benchmarks
+
+- **PERF-001**: [Benchmark criteria]
+- **PERF-002**: [Benchmark criteria]
+
+## Change Management
+
+### Update Process
+
+1. **Specification Update**: Modify this document first
+2. **Review & Approval**: [Approval process]
+3. **Implementation**: Apply changes to workflow
+4. **Testing**: [Validation approach]
+5. **Deployment**: [Release process]
+
+### Version History
+
+| Version | Date | Changes | Author |
+|---------|------|---------|--------|
+| 1.0 | [Date] | Initial specification | [Author] |
+
+## Related Specifications
+
+- [Link to related workflow specs]
+- [Link to infrastructure specs]
+- [Link to deployment specs]
+
+```
+
+## Analysis Instructions
+
+When analyzing the workflow file:
+
+1. **Extract Core Purpose**: Identify the primary business objective
+2. **Map Job Flow**: Create dependency graph showing execution order
+3. **Identify Contracts**: Document inputs, outputs, and interfaces
+4. **Capture Constraints**: Extract timeouts, permissions, and limits
+5. **Define Quality Gates**: Identify validation and approval points
+6. **Document Error Paths**: Map failure scenarios and recovery
+7. **Abstract Implementation**: Focus on behavior, not syntax
+
+## Mermaid Diagram Guidelines
+
+### Flow Types
+- **Sequential**: `A --> B --> C`
+- **Parallel**: `A --> B & A --> C; B --> D & C --> D`
+- **Conditional**: `A --> B{Decision}; B -->|Yes| C; B -->|No| D`
+
+### Styling
+```mermaid
+style TriggerNode fill:#e1f5fe
+style SuccessNode fill:#e8f5e8
+style FailureNode fill:#ffebee
+style ProcessNode fill:#f3e5f5
+```
+
+### Complex Workflows
+For workflows with 5+ jobs, use subgraphs:
+```mermaid
+graph TD
+    subgraph "Build Phase"
+        A[Lint] --> B[Test] --> C[Build]
+    end
+    subgraph "Deploy Phase"  
+        D[Staging] --> E[Production]
+    end
+    C --> D
+```
+
+## Token Optimization Strategies
+
+1. **Use Tables**: Dense information in structured format
+2. **Abbreviate Consistently**: Define once, use throughout
+3. **Bullet Points**: Avoid prose paragraphs
+4. **Code Blocks**: Structured data over narrative
+5. **Cross-Reference**: Link instead of repeat information
+
+Focus on creating a specification that serves as both documentation and a template for workflow updates.

package/skills/create-github-action-workflow-specification/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-github-action-workflow-specification`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/create-github-issue-feature-from-specification/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/create-github-issue-feature-from-specification/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: create-github-issue-feature-from-specification
+description: 'Create GitHub Issue for feature request from specification file using feature_request.yml template.'
+---
+
+# Create GitHub Issue from Specification
+
+Create GitHub Issue for the specification at `${file}`.
+
+## Process
+
+1. Analyze specification file to extract requirements
+2. Check existing issues using `search_issues`
+3. Create new issue using `create_issue` or update existing with `update_issue`
+4. Use `feature_request.yml` template (fallback to default)
+
+## Requirements
+
+- Single issue for the complete specification
+- Clear title identifying the specification
+- Include only changes required by the specification
+- Verify against existing issues before creation
+
+## Issue Content
+
+- Title: Feature name from specification
+- Description: Problem statement, proposed solution, and context
+- Labels: feature, enhancement (as appropriate)

package/skills/create-github-issue-feature-from-specification/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-github-issue-feature-from-specification`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/create-github-issues-feature-from-implementation-plan/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/create-github-issues-feature-from-implementation-plan/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: create-github-issues-feature-from-implementation-plan
+description: 'Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.'
+---
+
+# Create GitHub Issue from Implementation Plan
+
+Create GitHub Issues for the implementation plan at `${file}`.
+
+## Process
+
+1. Analyze plan file to identify phases
+2. Check existing issues using `search_issues`
+3. Create new issue per phase using `create_issue` or update existing with `update_issue`
+4. Use `feature_request.yml` or `chore_request.yml` templates (fallback to default)
+
+## Requirements
+
+- One issue per implementation phase
+- Clear, structured titles and descriptions
+- Include only changes required by the plan
+- Verify against existing issues before creation
+
+## Issue Content
+
+- Title: Phase name from implementation plan
+- Description: Phase details, requirements, and context
+- Labels: Appropriate for issue type (feature/chore)

package/skills/create-github-issues-feature-from-implementation-plan/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-github-issues-feature-from-implementation-plan`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/create-github-issues-for-unmet-specification-requirements/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/create-github-issues-for-unmet-specification-requirements/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: create-github-issues-for-unmet-specification-requirements
+description: 'Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.'
+---
+
+# Create GitHub Issues for Unmet Specification Requirements
+
+Create GitHub Issues for unimplemented requirements in the specification at `${file}`.
+
+## Process
+
+1. Analyze specification file to extract all requirements
+2. Check codebase implementation status for each requirement
+3. Search existing issues using `search_issues` to avoid duplicates
+4. Create new issue per unimplemented requirement using `create_issue`
+5. Use `feature_request.yml` template (fallback to default)
+
+## Requirements
+
+- One issue per unimplemented requirement from specification
+- Clear requirement ID and description mapping
+- Include implementation guidance and acceptance criteria
+- Verify against existing issues before creation
+
+## Issue Content
+
+- Title: Requirement ID and brief description
+- Description: Detailed requirement, implementation method, and context
+- Labels: feature, enhancement (as appropriate)
+
+## Implementation Check
+
+- Search codebase for related code patterns
+- Check related specification files in `/spec/` directory
+- Verify requirement isn't partially implemented

package/skills/create-github-issues-for-unmet-specification-requirements/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-github-issues-for-unmet-specification-requirements`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/create-github-pull-request-from-specification/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/create-github-pull-request-from-specification/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: create-github-pull-request-from-specification
+description: 'Create GitHub Pull Request for feature request from specification file using pull_request_template.md template.'
+---
+
+# Create GitHub Pull Request from Specification
+
+Create GitHub Pull Request for the specification at `${workspaceFolder}/.github/pull_request_template.md` .
+
+## Process
+
+1. Analyze specification file template from '${workspaceFolder}/.github/pull_request_template.md' to extract requirements by 'search' tool.
+2. Create pull request draft template by using 'create_pull_request' tool on to `${input:targetBranch}`. and make sure don't have any pull request of current branch was exist `get_pull_request`. If has continue to step 4, and skip step 3.
+3. Get changes in pull request by using 'get_pull_request_diff' tool to analyze information that was changed in pull Request.
+4. Update the pull request body and title created in the previous step using the 'update_pull_request' tool. Incorporate the information from the template obtained in the first step to update the body and title as needed.
+5. Switch from draft to ready for review by using 'update_pull_request' tool. To update state of pull request.
+6. Using 'get_me' to get username of person was created pull request and assign to `update_issue` tool. To assign pull request
+7. Response URL Pull request was create to user.
+
+## Requirements
+- Single pull request for the complete specification
+- Clear title/pull_request_template.md identifying the specification
+- Fill enough information into pull_request_template.md
+- Verify against existing pull requests before creation

package/skills/create-github-pull-request-from-specification/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/create-github-pull-request-from-specification`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/create-implementation-plan/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.