devskill 2.0.7 → 2.0.8

package/skills/github-copilot-starter/SKILL.md

@@ -0,0 +1,402 @@
+---
+name: github-copilot-starter
+description: 'Set up complete GitHub Copilot configuration for a new project based on technology stack'
+---
+
+You are a GitHub Copilot setup specialist. Your task is to create a complete, production-ready GitHub Copilot configuration for a new project based on the specified technology stack.
+
+## Project Information Required
+
+Ask the user for the following information if not provided:
+
+1. **Primary Language/Framework**: (e.g., JavaScript/React, Python/Django, Java/Spring Boot, etc.)
+2. **Project Type**: (e.g., web app, API, mobile app, desktop app, library, etc.)
+3. **Additional Technologies**: (e.g., database, cloud provider, testing frameworks, etc.)
+4. **Development Style**: (strict standards, flexible, specific patterns)
+5. **GitHub Actions / Coding Agent**: Does the project use GitHub Actions? (yes/no — determines whether to generate `copilot-setup-steps.yml`)
+
+## Configuration Files to Create
+
+Based on the provided stack, create the following files in the appropriate directories:
+
+### 1. `.github/copilot-instructions.md`
+Main repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.
+
+Use this structure:
+```md
+# {Project Name} — Copilot Instructions
+
+## Project Overview
+Brief description of what this project does and its primary purpose.
+
+## Tech Stack
+List the primary language, frameworks, and key dependencies.
+
+## Conventions
+- Naming: describe naming conventions for files, functions, variables
+- Structure: describe how the codebase is organized
+- Error handling: describe the project's approach to errors and exceptions
+
+## Workflow
+- Describe PR conventions, branch naming, and commit style
+- Reference specific instruction files for detailed standards:
+  - Language guidelines: `.github/instructions/{language}.instructions.md`
+  - Testing: `.github/instructions/testing.instructions.md`
+  - Security: `.github/instructions/security.instructions.md`
+  - Documentation: `.github/instructions/documentation.instructions.md`
+  - Performance: `.github/instructions/performance.instructions.md`
+  - Code review: `.github/instructions/code-review.instructions.md`
+```
+
+### 2. `.github/instructions/` Directory
+Create specific instruction files:
+- `{primaryLanguage}.instructions.md` - Language-specific guidelines
+- `testing.instructions.md` - Testing standards and practices
+- `documentation.instructions.md` - Documentation requirements
+- `security.instructions.md` - Security best practices
+- `performance.instructions.md` - Performance optimization guidelines
+- `code-review.instructions.md` - Code review standards and GitHub review guidelines
+
+### 3. `.github/skills/` Directory
+Create reusable skills as self-contained folders:
+- `setup-component/SKILL.md` - Component/module creation
+- `write-tests/SKILL.md` - Test generation
+- `code-review/SKILL.md` - Code review assistance
+- `refactor-code/SKILL.md` - Code refactoring
+- `generate-docs/SKILL.md` - Documentation generation
+- `debug-issue/SKILL.md` - Debugging assistance
+
+### 4. `.github/agents/` Directory
+Always create these 4 agents:
+- `software-engineer.agent.md`
+- `architect.agent.md`
+- `reviewer.agent.md`
+- `debugger.agent.md`
+
+For each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.
+
+**Agent Attribution**: When using content from awesome-copilot agents, add attribution comments:
+```markdown
+<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/agents/[filename].agent.md -->
+```
+
+### 5. `.github/workflows/` Directory (only if user uses GitHub Actions)
+Skip this section entirely if the user answered "no" to GitHub Actions.
+
+Create Coding Agent workflow file:
+- `copilot-setup-steps.yml` - GitHub Actions workflow for Coding Agent environment setup
+
+**CRITICAL**: The workflow MUST follow this exact structure:
+- Job name MUST be `copilot-setup-steps`
+- Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)
+- Set appropriate permissions (minimum required)
+- Customize steps based on the technology stack provided
+
+## Content Guidelines
+
+For each file, follow these principles:
+
+**MANDATORY FIRST STEP**: Always use the fetch tool to research existing patterns before creating any content:
+1. **Fetch specific instruction from awesome-copilot docs**: https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md
+2. **Fetch specific agents from awesome-copilot docs**: https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md
+3. **Fetch specific skills from awesome-copilot docs**: https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md
+4. **Check for existing patterns** that match the technology stack
+
+**Primary Approach**: Reference and adapt existing instructions from awesome-copilot repository:
+- **Use existing content** when available - don't reinvent the wheel
+- **Adapt proven patterns** to the specific project context
+- **Combine multiple examples** if the stack requires it
+- **ALWAYS add attribution comments** when using awesome-copilot content
+
+**Attribution Format**: When using content from awesome-copilot, add this comment at the top of the file:
+```md
+<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/instructions/[filename].instructions.md -->
+```
+
+**Examples:**
+```md
+<!-- Based on: https://github.com/github/awesome-copilot/blob/main/instructions/react.instructions.md -->
+---
+applyTo: "**/*.jsx,**/*.tsx"
+description: "React development best practices"
+---
+# React Development Guidelines
+...
+```
+
+```md
+<!-- Inspired by: https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md -->
+<!-- and: https://github.com/github/awesome-copilot/blob/main/instructions/spring-boot.instructions.md -->
+---
+applyTo: "**/*.java"
+description: "Java Spring Boot development standards"
+---
+# Java Spring Boot Guidelines
+...
+```
+
+**Secondary Approach**: If no awesome-copilot instructions exist, create **SIMPLE GUIDELINES ONLY**:
+- **High-level principles** and best practices (2-3 sentences each)
+- **Architectural patterns** (mention patterns, not implementation)
+- **Code style preferences** (naming conventions, structure preferences)
+- **Testing strategy** (approach, not test code)
+- **Documentation standards** (format, requirements)
+
+**STRICTLY AVOID in .instructions.md files:**
+- ❌ **Writing actual code examples or snippets**
+- ❌ **Detailed implementation steps**
+- ❌ **Test cases or specific test code**
+- ❌ **Boilerplate or template code**
+- ❌ **Function signatures or class definitions**
+- ❌ **Import statements or dependency lists**
+
+**CORRECT .instructions.md content:**
+- ✅ **"Use descriptive variable names and follow camelCase"**
+- ✅ **"Prefer composition over inheritance"**
+- ✅ **"Write unit tests for all public methods"**
+- ✅ **"Use TypeScript strict mode for better type safety"**
+- ✅ **"Follow the repository's established error handling patterns"**
+
+**Research Strategy with fetch tool:**
+1. **Check awesome-copilot first** - Always start here for ALL file types
+2. **Look for exact tech stack matches** (e.g., React, Node.js, Spring Boot)
+3. **Look for general matches** (e.g., frontend agents, testing skills, review workflows)
+4. **Check the docs and relevant directories directly** for related files
+5. **Prefer repo-native examples** over inventing new formats
+6. **Only create custom content** if nothing relevant exists
+
+**Fetch these awesome-copilot directories:**
+- **Instructions**: https://github.com/github/awesome-copilot/tree/main/instructions
+- **Agents**: https://github.com/github/awesome-copilot/tree/main/agents
+- **Skills**: https://github.com/github/awesome-copilot/tree/main/skills
+
+**Awesome-Copilot Areas to Check:**
+- **Frontend Web Development**: React, Angular, Vue, TypeScript, CSS frameworks
+- **C# .NET Development**: Testing, documentation, and best practices
+- **Java Development**: Spring Boot, Quarkus, testing, documentation
+- **Database Development**: PostgreSQL, SQL Server, and general database best practices
+- **Azure Development**: Infrastructure as Code, serverless functions
+- **Security & Performance**: Security frameworks, accessibility, performance optimization
+
+## File Structure Standards
+
+Ensure all files follow these conventions:
+
+```
+project-root/
+├── .github/
+│   ├── copilot-instructions.md
+│   ├── instructions/
+│   │   ├── [language].instructions.md
+│   │   ├── testing.instructions.md
+│   │   ├── documentation.instructions.md
+│   │   ├── security.instructions.md
+│   │   ├── performance.instructions.md
+│   │   └── code-review.instructions.md
+│   ├── skills/
+│   │   ├── setup-component/
+│   │   │   └── SKILL.md
+│   │   ├── write-tests/
+│   │   │   └── SKILL.md
+│   │   ├── code-review/
+│   │   │   └── SKILL.md
+│   │   ├── refactor-code/
+│   │   │   └── SKILL.md
+│   │   ├── generate-docs/
+│   │   │   └── SKILL.md
+│   │   └── debug-issue/
+│   │       └── SKILL.md
+│   ├── agents/
+│   │   ├── software-engineer.agent.md
+│   │   ├── architect.agent.md
+│   │   ├── reviewer.agent.md
+│   │   └── debugger.agent.md
+│   └── workflows/                        # only if GitHub Actions is used
+│       └── copilot-setup-steps.yml
+```
+
+## YAML Frontmatter Template
+
+Use this structure for all files:
+
+**Instructions (.instructions.md):**
+```md
+---
+applyTo: "**/*.{lang-ext}"
+description: "Development standards for {Language}"
+---
+# {Language} coding standards
+
+Apply the repository-wide guidance from `../copilot-instructions.md` to all code.
+
+## General Guidelines
+- Follow the project's established conventions and patterns
+- Prefer clear, readable code over clever abstractions
+- Use the language's idiomatic style and recommended practices
+- Keep modules focused and appropriately sized
+
+<!-- Adapt the sections below to match the project's specific technology choices and preferences -->
+```
+
+**Skills (SKILL.md):**
+```md
+---
+name: {skill-name}
+description: {Brief description of what this skill does}
+---
+
+# {Skill Name}
+
+{One sentence describing what this skill does. Always follow the repository's established patterns.}
+
+Ask for {required inputs} if not provided.
+
+## Requirements
+- Use the existing design system and repository conventions
+- Follow the project's established patterns and style
+- Adapt to the specific technology choices of this stack
+- Reuse existing validation and documentation patterns
+```
+
+**Agents (.agent.md):**
+```md
+---
+description: Generate an implementation plan for new features or refactoring existing code.
+tools: ['codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
+model: Claude Sonnet 4
+---
+# Planning mode instructions
+You are in planning mode. Your task is to generate an implementation plan for a new feature or for refactoring existing code.
+Don't make any code edits, just generate a plan.
+
+The plan consists of a Markdown document that describes the implementation plan, including the following sections:
+
+* Overview: A brief description of the feature or refactoring task.
+* Requirements: A list of requirements for the feature or refactoring task.
+* Implementation Steps: A detailed list of steps to implement the feature or refactoring task.
+* Testing: A list of tests that need to be implemented to verify the feature or refactoring task.
+```
+
+## Execution Steps
+
+1. **Gather project information** - Ask the user for technology stack, project type, and development style if not provided
+2. **Research awesome-copilot patterns**:
+   - Use the fetch tool to explore awesome-copilot directories
+   - Check instructions: https://github.com/github/awesome-copilot/tree/main/instructions
+   - Check agents: https://github.com/github/awesome-copilot/tree/main/agents (especially for matching expert agents)
+   - Check skills: https://github.com/github/awesome-copilot/tree/main/skills
+   - Document all sources for attribution comments
+3. **Create the directory structure**
+4. **Generate main copilot-instructions.md** with project-wide standards
+5. **Create language-specific instruction files** using awesome-copilot references with attribution
+6. **Generate reusable skills** tailored to project needs
+7. **Set up specialized agents**, fetching from awesome-copilot where applicable (especially for expert engineer agents matching the tech stack)
+8. **Create the GitHub Actions workflow for Coding Agent** (`copilot-setup-steps.yml`) — skip if user does not use GitHub Actions
+9. **Validate** all files follow proper formatting and include necessary frontmatter
+
+## Post-Setup Instructions
+
+After creating all files, provide the user with:
+
+1. **VS Code setup instructions** - How to enable and configure the files
+2. **Usage examples** - How to use each skill and agent
+3. **Customization tips** - How to modify files for their specific needs
+4. **Testing recommendations** - How to verify the setup works correctly
+
+## Quality Checklist
+
+Before completing, verify:
+- [ ] All authored Copilot markdown files have proper YAML frontmatter where required
+- [ ] Language-specific best practices are included
+- [ ] Files reference each other appropriately using Markdown links
+- [ ] Skills and agents include relevant descriptions; include MCP/tool-related metadata only when the target Copilot environment actually supports or requires it
+- [ ] Instructions are comprehensive but not overwhelming
+- [ ] Security and performance considerations are addressed
+- [ ] Testing guidelines are included
+- [ ] Documentation standards are clear
+- [ ] Code review standards are defined
+
+## Workflow Template Structure (only if GitHub Actions is used)
+
+The `copilot-setup-steps.yml` workflow MUST follow this exact format and KEEP IT SIMPLE:
+
+```yaml
+name: "Copilot Setup Steps"
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+  pull_request:
+    paths:
+      - .github/workflows/copilot-setup-steps.yml
+jobs:
+  # The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
+  copilot-setup-steps:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v5
+      # Add ONLY basic technology-specific setup steps here
+```
+
+**KEEP WORKFLOWS SIMPLE** - Only include essential steps:
+
+**Node.js/JavaScript:**
+```yaml
+- name: Set up Node.js
+  uses: actions/setup-node@v4
+  with:
+    node-version: "20"
+    cache: "npm"
+- name: Install dependencies
+  run: npm ci
+- name: Run linter
+  run: npm run lint
+- name: Run tests
+  run: npm test
+```
+
+**Python:**
+```yaml
+- name: Set up Python
+  uses: actions/setup-python@v4
+  with:
+    python-version: "3.11"
+- name: Install dependencies
+  run: pip install -r requirements.txt
+- name: Run linter
+  run: flake8 .
+- name: Run tests
+  run: pytest
+```
+
+**Java:**
+```yaml
+- name: Set up JDK
+  uses: actions/setup-java@v4
+  with:
+    java-version: "17"
+    distribution: "temurin"
+- name: Build with Maven
+  run: mvn compile
+- name: Run tests
+  run: mvn test
+```
+
+**AVOID in workflows:**
+- ❌ Complex configuration setups
+- ❌ Multiple environment configurations
+- ❌ Advanced tooling setup
+- ❌ Custom scripts or complex logic
+- ❌ Multiple package managers
+- ❌ Database setup or external services
+
+**INCLUDE only:**
+- ✅ Language/runtime setup
+- ✅ Basic dependency installation
+- ✅ Simple linting (if standard)
+- ✅ Basic test running
+- ✅ Standard build commands

package/skills/github-copilot-starter/SYNC.md

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

package/skills/github-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/github-issues/SKILL.md

@@ -0,0 +1,201 @@
+---
+name: github-issues
+description: 'Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.'
+---
+
+# GitHub Issues
+
+Manage GitHub issues using the `@modelcontextprotocol/server-github` MCP server.
+
+## Available Tools
+
+### MCP Tools (read operations)
+
+| Tool | Purpose |
+|------|---------|
+| `mcp__github__issue_read` | Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) |
+| `mcp__github__list_issues` | List and filter repository issues by state, labels, date |
+| `mcp__github__search_issues` | Search issues across repos using GitHub search syntax |
+| `mcp__github__projects_list` | List projects, project fields, project items, status updates |
+| `mcp__github__projects_get` | Get details of a project, field, item, or status update |
+| `mcp__github__projects_write` | Add/update/delete project items, create status updates |
+
+### CLI / REST API (write operations)
+
+The MCP server does not currently support creating, updating, or commenting on issues. Use `gh api` for these operations.
+
+| Operation | Command |
+|-----------|---------|
+| Create issue | `gh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=...` |
+| Update issue | `gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... -f state=...` |
+| Add comment | `gh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=...` |
+| Close issue | `gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed` |
+| Set issue type | Include `-f type=Bug` in the create call (REST API only, not supported by `gh issue create` CLI) |
+
+**Note:** `gh issue create` works for basic issue creation but does **not** support the `--type` flag. Use `gh api` when you need to set issue types.
+
+## Workflow
+
+1. **Determine action**: Create, update, or query?
+2. **Gather context**: Get repo info, existing labels, milestones if needed
+3. **Structure content**: Use appropriate template from [references/templates.md](references/templates.md)
+4. **Execute**: Use MCP tools for reads, `gh api` for writes
+5. **Confirm**: Report the issue URL to user
+
+## Creating Issues
+
+Use `gh api` to create issues. This supports all parameters including issue types.
+
+```bash
+gh api repos/{owner}/{repo}/issues \
+  -X POST \
+  -f title="Issue title" \
+  -f body="Issue body in markdown" \
+  -f type="Bug" \
+  --jq '{number, html_url}'
+```
+
+### Optional Parameters
+
+Add any of these flags to the `gh api` call:
+
+```
+-f type="Bug"                    # Issue type (Bug, Feature, Task, Epic, etc.)
+-f labels[]="bug"                # Labels (repeat for multiple)
+-f assignees[]="username"        # Assignees (repeat for multiple)
+-f milestone=1                   # Milestone number
+```
+
+**Issue types** are organization-level metadata. To discover available types, use:
+```bash
+gh api graphql -f query='{ organization(login: "ORG") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name'
+```
+
+**Prefer issue types over labels for categorization.** When issue types are available (e.g., Bug, Feature, Task), use the `type` parameter instead of applying equivalent labels like `bug` or `enhancement`. Issue types are the canonical way to categorize issues on GitHub. Only fall back to labels when the org has no issue types configured.
+
+### Title Guidelines
+
+- Be specific and actionable
+- Keep under 72 characters
+- When issue types are set, don't add redundant prefixes like `[Bug]`
+- Examples:
+  - `Login fails with SSO enabled` (with type=Bug)
+  - `Add dark mode support` (with type=Feature)
+  - `Add unit tests for auth module` (with type=Task)
+
+### Body Structure
+
+Always use the templates in [references/templates.md](references/templates.md). Choose based on issue type:
+
+| User Request | Template |
+|--------------|----------|
+| Bug, error, broken, not working | Bug Report |
+| Feature, enhancement, add, new | Feature Request |
+| Task, chore, refactor, update | Task |
+
+## Updating Issues
+
+Use `gh api` with PATCH:
+
+```bash
+gh api repos/{owner}/{repo}/issues/{number} \
+  -X PATCH \
+  -f state=closed \
+  -f title="Updated title" \
+  --jq '{number, html_url}'
+```
+
+Only include fields you want to change. Available fields: `title`, `body`, `state` (open/closed), `labels`, `assignees`, `milestone`.
+
+## Examples
+
+### Example 1: Bug Report
+
+**User**: "Create a bug issue - the login page crashes when using SSO"
+
+**Action**: 
+```bash
+gh api repos/github/awesome-copilot/issues \
+  -X POST \
+  -f title="Login page crashes when using SSO" \
+  -f type="Bug" \
+  -f body="## Description
+The login page crashes when users attempt to authenticate using SSO.
+
+## Steps to Reproduce
+1. Navigate to login page
+2. Click 'Sign in with SSO'
+3. Page crashes
+
+## Expected Behavior
+SSO authentication should complete and redirect to dashboard.
+
+## Actual Behavior
+Page becomes unresponsive and displays error." \
+  --jq '{number, html_url}'
+```
+
+### Example 2: Feature Request
+
+**User**: "Create a feature request for dark mode with high priority"
+
+**Action**:
+```bash
+gh api repos/github/awesome-copilot/issues \
+  -X POST \
+  -f title="Add dark mode support" \
+  -f type="Feature" \
+  -f labels[]="high-priority" \
+  -f body="## Summary
+Add dark mode theme option for improved user experience and accessibility.
+
+## Motivation
+- Reduces eye strain in low-light environments
+- Increasingly expected by users
+
+## Proposed Solution
+Implement theme toggle with system preference detection.
+
+## Acceptance Criteria
+- [ ] Toggle switch in settings
+- [ ] Persists user preference
+- [ ] Respects system preference by default" \
+  --jq '{number, html_url}'
+```
+
+## Common Labels
+
+Use these standard labels when applicable:
+
+| Label | Use For |
+|-------|---------|
+| `bug` | Something isn't working |
+| `enhancement` | New feature or improvement |
+| `documentation` | Documentation updates |
+| `good first issue` | Good for newcomers |
+| `help wanted` | Extra attention needed |
+| `question` | Further information requested |
+| `wontfix` | Will not be addressed |
+| `duplicate` | Already exists |
+| `high-priority` | Urgent issues |
+
+## Tips
+
+- Always confirm the repository context before creating issues
+- Ask for missing critical information rather than guessing
+- Link related issues when known: `Related to #123`
+- For updates, fetch current issue first to preserve unchanged fields
+
+## Extended Capabilities
+
+The following features require REST or GraphQL APIs beyond the basic MCP tools. Each is documented in its own reference file so the agent only loads the knowledge it needs.
+
+| Capability | When to use | Reference |
+|------------|-------------|-----------|
+| Advanced search | Complex queries with boolean logic, date ranges, cross-repo search, issue field filters (`field.name:value`) | [references/search.md](references/search.md) |
+| Sub-issues & parent issues | Breaking work into hierarchical tasks | [references/sub-issues.md](references/sub-issues.md) |
+| Issue dependencies | Tracking blocked-by / blocking relationships | [references/dependencies.md](references/dependencies.md) |
+| Issue types (advanced) | GraphQL operations beyond MCP `list_issue_types` / `type` param | [references/issue-types.md](references/issue-types.md) |
+| Projects V2 | Project boards, progress reports, field management | [references/projects.md](references/projects.md) |
+| Issue fields | Custom metadata: dates, priority, text, numbers (private preview) | [references/issue-fields.md](references/issue-fields.md) |
+| Images in issues | Embedding images in issue bodies and comments via CLI | [references/images.md](references/images.md) |

package/skills/github-issues/SYNC.md

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