Menu
Verify and add the required copyright header to DotSerial C# source files. Use when creating a new .cs file or when a file is missing the header.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | add-copyright-header |
| description | Verify and add the required copyright header to DotSerial C# source files. Use when creating a new .cs file or when a file is missing the header. |
Every .cs file in the DotSerial repository must start with the following header block.
The header must be the very first content in the file, before namespace, using, or any other statement.
Replace {FILENAME} with the actual file name (including .cs extension) and
{ONE LINE SUMMARY} with a concise single-line description of the file's purpose.
// -----------------------------------------------------------------------
// <copyright file="{FILENAME}" company="Piergiorgio Vagnozzi">
// Copyright (c) 2026 Piergiorgio Vagnozzi. All rights reserved.
// Licensed under the MIT License.
// See LICENSE file in the project root for full license information.
// </copyright>
// <summary>
// {ONE LINE SUMMARY}
// </summary>
// <created>2026-05-01</created>
// -----------------------------------------------------------------------
Search for files that do NOT start with the copyright block:
# Files in src/ missing the header
grep -rL "Copyright (c) 2026 Piergiorgio Vagnozzi" src/ --include="*.cs"
# Files in tests/ missing the header
grep -rL "Copyright (c) 2026 Piergiorgio Vagnozzi" tests/ --include="*.cs"
<created> date is always 2026-05-01 (project inception date) — do not change it.company attribute is always Piergiorgio Vagnozzi..cs files: source, tests, generated (if any).Debug failing GitHub Actions CI runs for DotSerial. Use when a CI build or test is failing on GitHub Actions and you need to understand why and fix it.
Format a Conventional Commits message for DotSerial changes. Use when asked to write a commit message, format a commit, or check if a message follows the project's commit conventions.
Build and test the DotSerial project. Use when asked to build, run tests, check CI status, or verify that changes don't break the build or test suite.
Step-by-step guide for adding a new platform implementation to DotSerial. Use when asked to add support for a new OS, transport, or connection type.
Pack and verify the DotSerial NuGet package. Use when asked to pack, publish, or verify the NuGet output for the DotSerial library.