devskill 2.0.7 → 2.0.8

package/skills/oo-component-documentation/assets/documentation-template.md

@@ -0,0 +1,97 @@
+---
+title: [Component Name] - Technical Documentation
+component_path: [Source component path]
+version: [Optional version]
+date_created: [YYYY-MM-DD]
+last_updated: [Optional YYYY-MM-DD]
+owner: [Optional team or individual]
+tags: [Optional list of relevant tags]
+---
+
+# [Component Name] Documentation
+
+[Concise introduction describing the component purpose and role in the system.]
+
+## 1. Component Overview
+
+### Purpose/Responsibility
+
+- OVR-001: State the component's primary responsibility
+- OVR-002: Define scope, including included and excluded responsibilities
+- OVR-003: Describe system context and major relationships
+
+## 2. Architecture Section
+
+- ARC-001: Document design patterns used
+- ARC-002: List internal and external dependencies with their purpose
+- ARC-003: Describe component interactions and relationships
+- ARC-004: Include visual diagrams where they clarify structure or behavior
+- ARC-005: Provide a Mermaid diagram showing structure, relationships, and dependencies
+
+### Component Structure and Dependencies Diagram
+
+Show the current:
+
+- Component structure
+- Internal dependencies
+- External dependencies
+- Data flow
+- Inheritance and composition relationships
+
+```mermaid
+graph TD
+    A[Primary Component] --> B[Collaborator]
+    A --> C[Dependency]
+```
+
+## 3. Interface Documentation
+
+- INT-001: Document public interfaces and usage patterns
+- INT-002: Provide a method or property reference table
+- INT-003: Cover events, callbacks, or notification mechanisms when applicable
+
+| Method/Property | Purpose | Parameters | Return Type | Usage Notes |
+|-----------------|---------|------------|-------------|-------------|
+| [Name] | [Purpose] | [Parameters] | [Type] | [Notes] |
+
+## 4. Implementation Details
+
+- IMP-001: Describe main implementation classes and responsibilities
+- IMP-002: Capture configuration requirements and initialization patterns
+- IMP-003: Summarize key algorithms or business logic
+- IMP-004: Note performance characteristics and bottlenecks
+
+## 5. Usage Examples
+
+### Basic Usage
+
+```text
+[Basic usage example aligned with the component language and API]
+```
+
+### Advanced Usage
+
+```text
+[Advanced configuration or orchestration example aligned with the current implementation]
+```
+
+- USE-001: Provide basic usage examples
+- USE-002: Show advanced configuration patterns
+- USE-003: Document best practices and recommended patterns
+
+## 6. Quality Attributes
+
+- QUA-001: Security
+- QUA-002: Performance
+- QUA-003: Reliability
+- QUA-004: Maintainability
+- QUA-005: Extensibility
+
+## 7. Reference Information
+
+- REF-001: List dependencies with versions and purposes where available
+- REF-002: Document configuration options
+- REF-003: Provide testing guidance and mock setup notes
+- REF-004: Capture troubleshooting notes and common issues
+- REF-005: Link related documentation
+- REF-006: Add change history or migration notes when relevant

package/skills/oo-component-documentation/references/create-mode.md

@@ -0,0 +1,32 @@
+# Create mode
+
+Use this workflow when the input is a component source path or the user asks to generate new documentation from code.
+
+## Input handling
+
+- Accept a single file or a folder path representing the component.
+- If the input is a folder, analyze the relevant source files in that folder and nearby supporting files.
+- If the input is a single file, treat it as the primary component entry point and inspect adjacent files as needed to understand collaborators and interfaces.
+
+## Create-specific requirements
+
+- Save the new documentation in `/docs/components/`.
+- Name the file `[component-name]-documentation.md`.
+- Set `component_path` to the source path provided by the user.
+- Set `date_created` to the current date.
+- Set `last_updated` only if the repository convention for the target area expects it at creation time.
+- Populate optional metadata such as `version`, `owner`, and `tags` only when they can be inferred reliably.
+
+## Create-specific analysis focus
+
+- Determine the primary component name and responsibilities from the code structure.
+- Identify the initial system context, scope boundaries, dependencies, design patterns, and collaboration model.
+- Build interface tables and usage examples from the actual public surface area.
+- Create a Mermaid diagram that introduces the component structure, dependencies, and data flow for a reader seeing the documentation for the first time.
+
+## Create-specific output guidance
+
+- Use the full section structure from `../assets/documentation-template.md`.
+- Write the introduction as a fresh overview of what the component does and why it exists.
+- Prefer complete sections over placeholders; if information is unavailable, mark the section with a short limitation note instead of leaving template text behind.
+- Include change history or migration notes only if there is evidence of prior versions or migration concerns in the code or repository history.

package/skills/oo-component-documentation/references/update-mode.md

@@ -0,0 +1,32 @@
+# Update mode
+
+Use this workflow when the input is an existing documentation Markdown file or the user asks to refresh existing component documentation.
+
+## Input handling
+
+- Read the existing documentation first to understand the current structure, terminology, and any front matter metadata.
+- Extract the component source path from the `component_path` front matter when present.
+- If `component_path` is missing, infer the component path from the documentation content and surrounding repository structure.
+- Use the current implementation as the source of truth when the documentation and code disagree.
+
+## Update-specific requirements
+
+- Preserve the existing documentation file as the output target.
+- Preserve `date_created`.
+- Update `last_updated` to the current date.
+- Preserve version history and ownership metadata when still accurate; refresh them only when the code or repository evidence indicates they have changed.
+- Maintain the existing organization where it is still useful, but ensure the content remains consistent with the shared template expectations.
+
+## Update-specific analysis focus
+
+- Compare the existing documentation with the current code to identify stale APIs, outdated diagrams, renamed dependencies, and changed usage patterns.
+- Highlight breaking changes, deprecated features, or major architectural shifts when they are evident.
+- Refresh method tables, examples, diagrams, dependency lists, and quality attribute notes to match the implementation as it exists today.
+- Add missing sections only when the component has grown or the current documentation omits information now needed for maintainers.
+
+## Update-specific output guidance
+
+- Keep useful editorial choices from the existing document, but remove stale or misleading content.
+- Update examples so they compile conceptually against the current API shape.
+- Refresh Mermaid diagrams rather than replacing them with generic placeholders.
+- Add migration notes or change history when the update reveals important compatibility or behavior changes.

package/skills/openapi-to-application-code/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/openapi-to-application-code/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: openapi-to-application-code
+description: 'Generate a complete, production-ready application from an OpenAPI specification'
+---
+
+# Generate Application from OpenAPI Spec
+
+Your goal is to generate a complete, working application from an OpenAPI specification using the active framework's conventions and best practices.
+
+## Input Requirements
+
+1. **OpenAPI Specification**: Provide either:
+   - A URL to the OpenAPI spec (e.g., `https://api.example.com/openapi.json`)
+   - A local file path to the OpenAPI spec
+   - The full OpenAPI specification content pasted directly
+
+2. **Project Details** (if not in spec):
+   - Project name and description
+   - Target framework and version
+   - Package/namespace naming conventions
+   - Authentication method (if not specified in OpenAPI)
+
+## Generation Process
+
+### Step 1: Analyze the OpenAPI Specification
+- Validate the OpenAPI spec for completeness and correctness
+- Identify all endpoints, HTTP methods, request/response schemas
+- Extract authentication requirements and security schemes
+- Note data model relationships and constraints
+- Flag any ambiguities or incomplete definitions
+
+### Step 2: Design Application Architecture
+- Plan directory structure appropriate for the framework
+- Identify controller/handler grouping by resource or domain
+- Design service layer organization for business logic
+- Plan data models and entity relationships
+- Design configuration and initialization strategy
+
+### Step 3: Generate Application Code
+- Create project structure with build/package configuration files
+- Generate models/DTOs from OpenAPI schemas
+- Generate controllers/handlers with route mappings
+- Generate service layer with business logic
+- Generate repository/data access layer if applicable
+- Add error handling, validation, and logging
+- Generate configuration and startup code
+
+### Step 4: Add Supporting Files
+- Generate appropriate unit tests for services and controllers
+- Create README with setup and running instructions
+- Add .gitignore and environment configuration templates
+- Generate API documentation files
+- Create example requests/integration tests
+
+## Output Structure
+
+The generated application will include:
+
+```
+project-name/
+├── README.md                      # Setup and usage instructions
+├── [build-config]                 # Framework-specific build files (pom.xml, build.gradle, package.json, etc.)
+├── src/
+│   ├── main/
+│   │   ├── [language]/
+│   │   │   ├── controllers/       # HTTP endpoint handlers
+│   │   │   ├── services/          # Business logic
+│   │   │   ├── models/            # Data models and DTOs
+│   │   │   ├── repositories/      # Data access (if applicable)
+│   │   │   └── config/            # Application configuration
+│   │   └── resources/             # Configuration files
+│   └── test/
+│       ├── [language]/
+│       │   ├── controllers/       # Controller tests
+│       │   └── services/          # Service tests
+│       └── resources/             # Test configuration
+├── .gitignore
+├── .env.example                   # Environment variables template
+└── docker-compose.yml             # Optional: Docker setup (if applicable)
+```
+
+## Best Practices Applied
+
+- **Framework Conventions**: Follows framework-specific naming, structure, and patterns
+- **Separation of Concerns**: Clear layers with controllers, services, and repositories
+- **Error Handling**: Comprehensive error handling with meaningful responses
+- **Validation**: Input validation and schema validation throughout
+- **Logging**: Structured logging for debugging and monitoring
+- **Testing**: Unit tests for services and controllers
+- **Documentation**: Inline code documentation and setup instructions
+- **Security**: Implements authentication/authorization from OpenAPI spec
+- **Scalability**: Design patterns support growth and maintenance
+
+## Next Steps
+
+After generation:
+
+1. Review the generated code structure and make customizations as needed
+2. Install dependencies according to framework requirements
+3. Configure environment variables and database connections
+4. Run tests to verify generated code
+5. Start the development server
+6. Test endpoints using the provided examples
+
+## Questions to Ask if Needed
+
+- Should the application include database/ORM setup, or just in-memory/mock data?
+- Do you want Docker configuration for containerization?
+- Should authentication be JWT, OAuth2, API keys, or basic auth?
+- Do you need integration tests or just unit tests?
+- Any specific database technology preferences?
+- Should the API include pagination, filtering, and sorting examples?

package/skills/openapi-to-application-code/SYNC.md

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

package/skills/pdftk-server/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/pdftk-server/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: pdftk-server
+description: 'Skill for using the command-line tool pdftk (PDFtk Server) for working with PDF files. Use when asked to merge PDFs, split PDFs, rotate pages, encrypt or decrypt PDFs, fill PDF forms, apply watermarks, stamp overlays, extract metadata, burst documents into pages, repair corrupted PDFs, attach or extract files, or perform any PDF manipulation from the command line.'
+---
+
+# PDFtk Server
+
+PDFtk Server is a command-line tool for working with PDF documents. It can merge, split, rotate, encrypt, decrypt, watermark, stamp, fill forms, extract metadata, and manipulate PDFs in a variety of ways.
+
+## When to Use This Skill
+
+- Merging or joining multiple PDF files into one
+- Splitting or bursting a PDF into individual pages
+- Rotating PDF pages
+- Encrypting or decrypting PDF files
+- Filling PDF form fields from FDF/XFDF data
+- Applying background watermarks or foreground stamps
+- Extracting PDF metadata, bookmarks, or form field information
+- Repairing corrupted PDF files
+- Attaching or extracting files embedded in PDFs
+- Removing specific pages from a PDF
+- Collating separately scanned even/odd pages
+- Compressing or decompressing PDF page streams
+
+## Prerequisites
+
+- PDFtk Server must be installed on the system
+  - **Windows**: `winget install --id PDFLabs.PDFtk.Server`
+  - **macOS**: `brew install pdftk-java`
+  - **Linux (Debian/Ubuntu)**: `sudo apt-get install pdftk`
+  - **Linux (Red Hat/Fedora)**: `sudo dnf install pdftk`
+- Access to a terminal or command prompt
+- Verify installation by running `pdftk --version`
+
+## Step-by-Step Workflows
+
+### Merge Multiple PDFs
+
+```bash
+pdftk file1.pdf file2.pdf cat output merged.pdf
+```
+
+Using handles for more control:
+
+```bash
+pdftk A=file1.pdf B=file2.pdf cat A B output merged.pdf
+```
+
+### Split a PDF into Individual Pages
+
+```bash
+pdftk input.pdf burst
+```
+
+### Extract Specific Pages
+
+Extract pages 1-5 and 10-15:
+
+```bash
+pdftk input.pdf cat 1-5 10-15 output extracted.pdf
+```
+
+### Remove Specific Pages
+
+Remove page 13:
+
+```bash
+pdftk input.pdf cat 1-12 14-end output output.pdf
+```
+
+### Rotate Pages
+
+Rotate all pages 90 degrees clockwise:
+
+```bash
+pdftk input.pdf cat 1-endeast output rotated.pdf
+```
+
+### Encrypt a PDF
+
+Set an owner password and a user password with 128-bit encryption (default):
+
+```bash
+pdftk input.pdf output secured.pdf owner_pw mypassword user_pw userpass
+```
+
+### Decrypt a PDF
+
+Remove encryption using the known password:
+
+```bash
+pdftk secured.pdf input_pw mypassword output unsecured.pdf
+```
+
+### Fill a PDF Form
+
+Populate form fields from an FDF file and flatten to prevent further edits:
+
+```bash
+pdftk form.pdf fill_form data.fdf output filled.pdf flatten
+```
+
+### Apply a Background Watermark
+
+Place a single-page PDF behind every page of the input (input should have transparency):
+
+```bash
+pdftk input.pdf background watermark.pdf output watermarked.pdf
+```
+
+### Stamp an Overlay
+
+Place a single-page PDF on top of every page of the input:
+
+```bash
+pdftk input.pdf stamp overlay.pdf output stamped.pdf
+```
+
+### Extract Metadata
+
+Export bookmarks, page metrics, and document information:
+
+```bash
+pdftk input.pdf dump_data output metadata.txt
+```
+
+### Repair a Corrupted PDF
+
+Pass a broken PDF through pdftk to attempt automatic repair:
+
+```bash
+pdftk broken.pdf output fixed.pdf
+```
+
+### Collate Scanned Pages
+
+Interleave separately scanned even and odd pages:
+
+```bash
+pdftk A=even.pdf B=odd.pdf shuffle A B output collated.pdf
+```
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| `pdftk` command not found | Verify installation; check that pdftk is in your system PATH |
+| Cannot decrypt PDF | Ensure you are providing the correct owner or user password via `input_pw` |
+| Output file is empty or corrupt | Check input file integrity; try running `pdftk input.pdf output repaired.pdf` first |
+| Form fields not visible after fill | Use the `flatten` flag to merge fields into the page content |
+| Watermark not appearing | Ensure the input PDF has transparent regions; use `stamp` for opaque overlays |
+| Permission denied errors | Check file permissions on input and output paths |
+
+## References
+
+Bundled reference documents in the `references/` folder:
+
+- [pdftk-man-page.md](references/pdftk-man-page.md) - Complete manual reference with all operations, options, and syntax
+- [pdftk-cli-examples.md](references/pdftk-cli-examples.md) - Practical command-line examples for common tasks
+- [download.md](references/download.md) - Installation and download instructions for all platforms
+- [pdftk-server-license.md](references/pdftk-server-license.md) - PDFtk Server licensing information
+- [third-party-materials.md](references/third-party-materials.md) - Third-party library licenses

package/skills/pdftk-server/SYNC.md

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

package/skills/pdftk-server/references/download.md

@@ -0,0 +1,75 @@
+# Download
+
+PDFtk provides an installer for Windows. Many Linux distributions provide a PDFtk package you can download and install using their package manager.
+
+## Microsoft Windows
+
+Download the PDFtk Server installer for Windows 10 and 11 using the following command:
+
+```bash
+winget install --id PDFLabs.PDFtk.Server
+```
+
+Then run the installer:
+
+```bash
+.\pdftk_server-2.02-win-setup.exe
+```
+
+After installation, open a command prompt, type `pdftk` and press Enter. PDFtk will respond by displaying brief usage information.
+
+## Linux
+
+On Debian/Ubuntu-based distributions:
+
+```bash
+sudo apt-get install pdftk
+```
+
+On Red Hat/Fedora-based distributions:
+
+```bash
+sudo dnf install pdftk
+```
+
+## PDFtk Server GPL License
+
+PDFtk Server (pdftk) is not public domain software. It can be installed and used at no charge under its [GNU General Public License (GPL) Version 2](https://www.pdflabs.com/docs/pdftk-license/gnu_general_public_license_2.txt). PDFtk uses third-party libraries. The [licenses and source code for these libraries are described here](https://www.pdflabs.com/docs/pdftk-license/) under Third-Party Materials.
+
+## PDFtk Server Redistribution License
+
+If you plan to distribute PDFtk Server as part of your own software, you will need a PDFtk Server Redistribution License. The exception to this rule is if your software is licensed to the public under the GPL or another compatible license.
+
+The commercial redistribution license allows you, subject to the terms of the license, to distribute an unlimited number of PDFtk Server binaries as part of one distinct commercial product. Please read the full license:
+
+[PDFtk Server Redistribution License (PDF)](https://pdflabs.onfastspring.com/pdftk-server)
+
+Now available for $995:
+
+[PDFtk Server Redistribution License](https://www.pdflabs.com/docs/pdftk-license/)
+
+## Build PDFtk Server from Source
+
+PDFtk Server can be compiled from its source code. PDFtk Server is known to compile and run on [Debian](https://packages.debian.org/search?keywords=pdftk), [Ubuntu Linux](https://packages.ubuntu.com/search?keywords=pdftk), [FreeBSD](https://www.freshports.org/print/pdftk/), Slackware Linux, SuSE, Solaris and [HP-UX](http://hpux.connect.org.uk/hppd/hpux/Text/pdftk-1.45/).
+
+Download and unpack the source:
+
+```bash
+curl -LO https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk-2.02-src.zip
+unzip pdftk-2.02-src.zip
+```
+
+Review the [pdftk license information](https://www.pdflabs.com/docs/pdftk-license/) in: `license_gpl_pdftk/readme.txt`.
+
+Review the Makefile provided for your platform and confirm that `TOOLPATH` and `VERSUFF` suit your installation of gcc/gcj/libgcj. If you run `apropos gcc` and it returns something like `gcc-4.5`, then set `VERSUFF` to `-4.5`. The `TOOLPATH` probably does not need to be set.
+
+Change into the `pdftk` sub-directory and run:
+
+```bash
+cd pdftk
+make -f Makefile.Debian
+```
+
+Substitute your platform's Makefile filename as needed.
+
+PDFtk has been built using gcc/gcj/libgcj versions 3.4.5, 4.4.1, 4.5.0, and 4.6.3. PDFtk 1.4x fails to build on gcc 3.3.5 due to missing libgcj features. If you are using gcc 3.3 or older, try building [pdftk 1.12](https://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/pdftk-1.12.tar.gz) instead.