Add Analyzer
dotnet/roslynator
A skill your agent uses when adding a new RCS diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator EditorConfig options, or when docs say CHANGELOG.md…
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
Install Maintain DisCatSharp
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharp --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/maintain-discatsharp .claude/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .claude/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharp --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/maintain-discatsharp .agents/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .agents/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharp --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/maintain-discatsharp .cursor/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .cursor/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Aiko-IT-Systems/DisCatSharp.git --path skills/maintain-discatsharp--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharp --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/maintain-discatsharp .gemini/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .gemini/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/maintain-discatsharp .github/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .github/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Aiko-IT-Systems/DisCatSharp maintain-discatsharp --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Aiko-IT-Systems/DisCatSharp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/maintain-discatsharp .opencode/skills/maintain-discatsharp && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maintain-discatsharp" agent skill from https://github.com/Aiko-IT-Systems/DisCatSharp/tree/main/skills/maintain-discatsharp into .opencode/skills/maintain-discatsharp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-discatsharp", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maintain-discatsharp- GitHub stars
- 140
- Token cost
- ~1.2k tokens
- SKILL.md length
- 553 words
- Files
- 4 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
- Works in 5 steps: Read the repository's root AGENTS.md and… → Confirm the exact checkout, branch,… → Treat existing tracked and untracked… → …
- Adding or changing a Discord payload model or API member in DisCatSharp
- SKILL.md covers Start safely, Trace the behavior, Implement consistently and Validate proportionally, plus 2 more sections
- Calls git
What it does
The skill works on a live checkout of the DisCatSharp repository and starts by reading AGENTS.md and CONTRIBUTING.md and confirming the branch, the issue or PR and the state of the working tree. Existing tracked and untracked changes are treated as the user's and never discarded, files are re-read just before patching in case someone else is editing, and the discatsharp-ai.xml Repomix snapshot is read-only and may be out of date.
Before touching a public member or payload field, it traces the whole behavior: input parsing and type mapping, constructors and defaults, JSON handling and Optional<T>, copies and builders, equality and cache updates, REST and Gateway models, XML documentation, analyzers, migrations and a focused regression test. It follows the repository's C# style, avoids breaking changes where it can, uses the Deprecated path for public removals and aims to document every declaration. A references folder holds a repository map and a validation matrix.
When your agent uses it
- Adding or changing a Discord payload model or API member in DisCatSharp
- Fixing serialization, command synchronization or Gateway dispatch bugs
- Preparing release notes, DocFX output or a pull request for the repository
- Reviewing a change for compatibility across the supported target frameworks
Example prompts
- “Add the new forum tag field to the channel model in DisCatSharp and trace it through serialization.”
- “Why does application command synchronization overwrite my changes? Fix it and add a regression test.”
- “Review this PR to DisCatSharp for missing XML docs and breaking public API changes.”
- “Prepare release notes for the next DisCatSharp version.”
Requirements
- A checkout of the DisCatSharp repository
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the repository's root AGENTS.md and CONTRIBUTING.md.
- Confirm the exact checkout, branch, target issue or PR, and working-tree state.
- Treat existing tracked and untracked changes as user-owned. Never discard, rewrite, or include unrelated work.
- Re-read files immediately before patching when another person or agent may be editing concurrently.
- Use live files and current supplied upstream documentation as authoritative. discatsharp-ai.xml is a read-only Repomix snapshot and may be…
What it can do on your machine
Read from SKILL.md and the folder at commit aeb1c40. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Maintain DisCatSharp loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 553 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Aiko-IT-Systems/DisCatSharp at commit aeb1c40, republished under its MIT licence (© Aiko-IT-Systems). 553 words, ~1,178 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-discatsharp/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- maintain-discatsharp
- description
- Review, modify, test, document, or release the DisCatSharp repository. Use for DisCatSharp source changes, API additions and migrations, Discord payload models, serialization, command synchronization, Gateway dispatch, REST behavior, analyzer work, multi-target testing, DocFX generation, release notes, and repository pull requests.
- license
- MIT
Maintain DisCatSharp
Make evidence-backed changes against the live checkout. Preserve user work, trace every connected behavior that carries a public value, and validate the smallest relevant surface across the supported frameworks.
Start safely
- Read the repository's root
AGENTS.mdandCONTRIBUTING.md. - Confirm the exact checkout, branch, target issue or PR, and working-tree state.
- Treat existing tracked and untracked changes as user-owned. Never discard, rewrite, or include unrelated work.
- Re-read files immediately before patching when another person or agent may be editing concurrently.
- Use live files and current supplied upstream documentation as authoritative.
discatsharp-ai.xmlis a read-only Repomix snapshot and may be stale.
Read references/repository-map.md before changing an unfamiliar subsystem.
Trace the behavior
Do not review a public member or payload field in isolation. Depending on the feature, inspect:
- Input parsing and type mapping.
- Constructors, property setters, validation, and default values.
- JSON serialization/deserialization and
Optional<T>behavior. - Manual copies, localization reconstruction, cloning, and builders.
- Equality, synchronization, overwrite, and cache-update decisions.
- REST request models and Gateway payload/event models.
- XML documentation for public, internal, and private symbols, plus conceptual guidance, analyzers, and migrations.
- Focused regression tests for the failure mode.
Mirror Discord's actual contract. Do not add speculative REST enrichment to a Gateway event when its payload already carries the authoritative data.
Implement consistently
- Follow the repository's C# style, including file-scoped namespaces and existing
this.usage. - Preserve compatibility. Discuss breaking changes and prefer the repository's
Deprecatedmigration path for public API removal. - Use exact current upstream documentation when Discord behavior is revision-sensitive.
- Maintain the repository's 100% documentation goal. Every declaration is in scope regardless of visibility, including internal and private types, members, and fields. New and materially changed code must not add undocumented declarations; explain state invariants and ownership rather than restating names, and improve adjacent gaps when practical.
- Keep REST bucket ordering distinct from Gateway dispatch ordering.
- Avoid broad redesign during a focused fix unless a connected correctness path requires it.
- Use
apply_patchor an equally reviewable edit path and inspect the resulting diff.
Show full SKILL.md (218 more words)Show less
Validate proportionally
Read references/validation-matrix.md, then:
- Run the smallest relevant test project or filtered regression tests.
- Cover
net9.0,net10.0, andnet11.0when the project targets all three. - Build the affected package or solution when public/API shape changes.
- Run
git diff --checkand inspect untracked files separately from the diff stat. - For Gateway tests that immediately inspect callbacks, select
SequentialHandlersor explicitly wait for concurrent handlers to complete. - Run broader tests only when the touched dependency surface justifies them.
Documentation and release work
- Generate documentation with
docfx DisCatSharp.Docs/docfx.json; do not manually maintain generated API navigation. - Keep conceptual content discoverable through DocFX rather than hardcoded search-index folder lists.
- Update XML documentation across every affected visibility level and add migration guidance for behavioral or breaking changes.
- Keep
RELEASENOTES.mdas the active cumulative release-cycle notes. - Treat
CHANGELOG.mdas the stable release index and DocFX changelog pages as the detailed historical record. - Public releases are created only through the manually dispatched
Release DisCatSharpworkflow.
Hand off cleanly
- State what changed, what was verified, and any remaining risk.
- Do not claim a timed-out command failed without checking the process or its output.
- Follow the repository's pull-request template and requested draft/merge boundary.
- Never merge, publish a package, enable repository policy, or mutate production infrastructure unless the user explicitly authorizes it.
© Aiko-IT-Systems, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/maintain-discatsharp of Aiko-IT-Systems/DisCatSharp.
- SKILL.md
- agents/openai.yaml
- references/repository-map.md
- references/validation-matrix.md
Open the folder on GitHubat commit aeb1c40
Compare with similar skills
Maintain DisCatSharp next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Maintain DisCatSharp this skillAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Add Analyzerdotnet/roslynator | 3.5k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Opik Documentation Patternscomet-ml/opik | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewjonathanpeppers/dotnes | 780 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Release Roslynatordotnet/roslynator | 3.5k | — | ~1k | Automated safety check: Pass | Custom licence | |
| ScottPlot Cookbook RecipeScottPlot/ScottPlot | 6.8k | — | ~384 | Automated safety check: Pass | MIT |
Similar skills
- Official
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
Code Review
jonathanpeppers/dotnes
Review dotnes pull requests against established repository rules.
- Official
Release Roslynator
dotnet/roslynator
A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.
ScottPlot Cookbook Recipe
ScottPlot/ScottPlot
Adds or extends a ScottPlot Cookbook recipe for a given plottable, in the right PlotTypes category and in the style of neighboring recipes.
- Official
Gh Stack
dotnet/macios
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension.
More from Aiko-IT-Systems/DisCatSharp
DisCatSharp Discord Development
Aiko-IT-Systems/DisCatSharp
Helps build, explain and troubleshoot C# Discord apps on DisCatSharp, answering from the project's installed version and the library's documentation rather than guesses.
Related
Categories
Questions about Maintain DisCatSharp
What does Maintain DisCatSharp do?
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks. md and confirming the branch, the issue or PR and the state of the working tree.xml Repomix snapshot is read-only and may be out of date.
When should I use Maintain DisCatSharp?
Maintain DisCatSharp fits situations like: adding or changing a Discord payload model or API member in DisCatSharp; fixing serialization, command synchronization or Gateway dispatch bugs; preparing release notes, DocFX output or a pull request for the repository; reviewing a change for compatibility across the supported target frameworks.
How do I install Maintain DisCatSharp in Claude Code?
Run `npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a claude-code`. Or copy the skill folder (skills/maintain-discatsharp in Aiko-IT-Systems/DisCatSharp) into .claude/skills/maintain-discatsharp in your project. Claude Code loads it when a task matches its description.
How do I install Maintain DisCatSharp in Codex?
Run `npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a codex`. Or copy the skill folder (skills/maintain-discatsharp in Aiko-IT-Systems/DisCatSharp) into .agents/skills/maintain-discatsharp in your project. Codex loads it when a task matches its description.
Can I use Maintain DisCatSharp in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Aiko-IT-Systems/DisCatSharp --skill maintain-discatsharp -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-discatsharp, .gemini/skills/maintain-discatsharp, .github/skills/maintain-discatsharp and .opencode/skills/maintain-discatsharp in your project.
What does Maintain DisCatSharp need to run?
Going by SKILL.md and its folder, Maintain DisCatSharp needs the command-line tools its instructions call (git). Our summary lists: A checkout of the DisCatSharp repository.
Does Maintain DisCatSharp access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Maintain DisCatSharp safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Maintain DisCatSharp use?
Maintain DisCatSharp is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain DisCatSharp use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 584 tokens, read only when the agent opens those files.
What are the alternatives to Maintain DisCatSharp?
Skills that share tags, products or a category with Maintain DisCatSharp: Add Analyzer (dotnet/roslynator, 3.5k stars), Opik Documentation Patterns (comet-ml/opik, 22k stars), Code Review (jonathanpeppers/dotnes, 780 stars) and Release Roslynator (dotnet/roslynator, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain DisCatSharp?
Aiko-IT-Systems (a GitHub organization) maintains it in Aiko-IT-Systems/DisCatSharp, which has 140 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.
Source: Aiko-IT-Systems/DisCatSharp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.