Code Audit
3stoneBrother/code-audit
Professional code security audit skill covering 55+ vulnerability types.
Ensure that C and C++/CLI types are documented with XML comments and follow best practices for documentation.
Install Doc Comments
$ npx skills add MichaelGrafnetter/DSInternals --skill doc-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MichaelGrafnetter/DSInternals doc-comments --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/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/doc-comments .claude/skills/doc-comments && 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 "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .claude/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-commentsType 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 MichaelGrafnetter/DSInternals --skill doc-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MichaelGrafnetter/DSInternals doc-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/doc-comments .agents/skills/doc-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .agents/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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 MichaelGrafnetter/DSInternals --skill doc-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MichaelGrafnetter/DSInternals doc-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/doc-comments .cursor/skills/doc-comments && 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 "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .cursor/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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/MichaelGrafnetter/DSInternals.git --path .agents/skills/doc-comments--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 MichaelGrafnetter/DSInternals --skill doc-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MichaelGrafnetter/DSInternals doc-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/doc-comments .gemini/skills/doc-comments && 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 "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .gemini/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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 MichaelGrafnetter/DSInternals doc-commentsInstalls 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 MichaelGrafnetter/DSInternals --skill doc-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/doc-comments .github/skills/doc-comments && 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 "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .github/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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 MichaelGrafnetter/DSInternals --skill doc-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MichaelGrafnetter/DSInternals doc-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MichaelGrafnetter/DSInternals.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/doc-comments .opencode/skills/doc-comments && 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 "doc-comments" agent skill from https://github.com/MichaelGrafnetter/DSInternals/tree/master/.agents/skills/doc-comments into .opencode/skills/doc-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-comments", 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
doc-comments- GitHub stars
- 2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 680 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Ensure that C and C++/CLI types are documented with XML comments and follow best practices for documentation.
- Security work in your project
- SKILL.md covers Guidance for all APIs, Methods, Constructors and Properties, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Doc Comments is an agent skill from MichaelGrafnetter/DSInternals. Ensure that C and C++/CLI types are documented with XML comments and follow best practices for documentation.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security. It works with C# and C++. The repository describes itself as: Directory Services Internals (DSInternals) PowerShell Module and Framework. The licence is MIT.
When your agent uses it
- Security work in your project
Example prompts
- “/doc-comments”
What it can do on your machine
Read from SKILL.md and the folder at commit 917bc84. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Doc Comments loads about 1.2k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 680 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 MichaelGrafnetter/DSInternals at commit 917bc84, republished under its MIT licence (© MichaelGrafnetter). 680 words, ~1,242 tokens.
Download SKILL.mdSave it as
.claude/skills/doc-comments/SKILL.md (or your agent's skills folder).- name
- doc-comments
- description
- Ensure that C# and C++/CLI types are documented with XML comments and follow best practices for documentation.
C# and C++/CLI Documentation Best Practices
- All public members in the entire solution should be documented with XML comments.
- It is encouraged to document internal members as well, especially if they are complex or not self-explanatory.
Guidance for all APIs
- Use
<summary>to provide a brief, one sentence, description of what the type or member does. Start the summary with a present-tense, third-person verb. - Use
<remarks>for additional information, which can include implementation details, usage notes, or any other relevant context. - Use
<see langword>for language-specific keywords likenull,true,false,int,bool, etc. - Use
<c>for inline code snippets. - Use
<example>for usage examples on how to use the member.- Use
<code>for code blocks.<code>tags should be placed within an<example>tag. Add the language of the code example using thelanguageattribute, for example,<code language="csharp">.
- Use
- Use
<see cref>to reference other types or members inline (in a sentence). - Use
<seealso>for standalone (not in a sentence) references to other types or members in the "See also" section of the online docs. - Use
<inheritdoc/>to inherit documentation from base classes or interfaces.- Unless there is major behavior change, in which case you should document the differences.
Methods
- Use
<param>to describe method parameters.- The description should be a noun phrase that doesn't specify the data type.
- Begin with an introductory article.
- If the parameter is a flag enum, start the description with "A bitwise combination of the enumeration values that specifies...".
- If the parameter is a non-flag enum, start the description with "One of the enumeration values that specifies...".
- If the parameter is a Boolean, the wording should be of the form "
<see langword="true" />to ...; otherwise,<see langword="false" />.". - If the parameter is an "out" parameter, the wording should be of the form "When this method returns, contains .... This parameter is treated as uninitialized.".
- Use
<paramref>to reference parameter names in documentation. - Use
<typeparam>to describe type parameters in generic types or methods. - Use
<typeparamref>to reference type parameters in documentation. - Use
<returns>to describe what the method returns.- The description should be a noun phrase that doesn't specify the data type.
- Begin with an introductory article.
- If the return type is Boolean, the wording should be of the form "
<see langword="true" />if ...; otherwise,<see langword="false" />.".
Constructors
- The summary wording should be "Initializes a new instance of the
<Class>class [or struct].".
Show full SKILL.md (285 more words)Show less
Properties
- The
<summary>should start with:- "Gets or sets..." for a read-write property.
- "Gets..." for a read-only property.
- "Gets [or sets] a value that indicates whether..." for properties that return a Boolean value.
- Use
<value>to describe the value of the property.- The description should be a noun phrase that doesn't specify the data type.
- If the property has a default value, add it in a separate sentence, for example, "The default is
<see langword="false" />". - If the value type is Boolean, the wording should be of the form "
<see langword="true" />if ...; otherwise,<see langword="false" />. The default is ...".
Exceptions
- Use
<exception cref>to document exceptions thrown by constructors, properties, indexers, methods, operators, and events. - Document all exceptions thrown directly by the member.
- For exceptions thrown by nested members, document only the exceptions users are most likely to encounter.
- The description of the exception describes the condition under which it's thrown.
- Omit "Thrown if ..." or "If ..." at the beginning of the sentence. Just state the condition directly, for example "An error occurred when accessing a Message Queuing API."
C++/CLI Specific Guidelines
C++/CLI uses the same XML documentation syntax as C#, with minor differences:
- Use triple-slash (
///) comments before declarations. - In C++/CLI, XML doc comments must appear immediately before the declaration (no blank lines between the comment and the code).
- Use
<summary>,<param>,<returns>,<remarks>,<exception>, and other tags exactly as in C#. - For managed types (ref class, value class), document the same way as C# classes and structs.
- For native types exposed to managed code, ensure XML comments are added to the managed wrappers.
- Use
<see cref="ClassName::MemberName" />syntax for cross-references in C++/CLI (note the::scope resolution operator). - When documenting interop code, include
<remarks>explaining any native/managed boundary considerations.
© MichaelGrafnetter, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/doc-comments of MichaelGrafnetter/DSInternals.
Open the folder on GitHubat commit 917bc84
Compare with similar skills
Doc Comments 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 |
|---|---|---|---|---|---|---|
| Doc Comments this skillMichaelGrafnetter/DSInternals | 2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Code Audit3stoneBrother/code-audit | 893 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| Constant Time Analysissickn33/agentic-awesome-skills | 47k | 2 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Fory Performance Optimizationapache/fory | 4.6k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| MCP Debuggerdebugmcp/mcp-debugger | 171 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Validate GsdkPlayFab/gsdk | 170 | — | ~645 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Constant Time Analysis
sickn33/agentic-awesome-skills
Analyze cryptographic code to detect operations that leak secret data through execution timing variations.
Fory Performance Optimization
apache/fory
Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python/Cython, Go, Rust, Swift, C, JavaScript/TypeScript, Dart, Kotlin, Scala).
MCP Debugger
debugmcp/mcp-debugger
A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…
Validate Gsdk
PlayFab/gsdk
Validates PlayFab Game Server SDK (GSDK) integrations in game server projects.
Rsid SDK
realsenseai/RealSenseID
RealSenseID face authentication SDK reference. An agent skill from realsenseai/RealSenseID.
More from MichaelGrafnetter/DSInternals
Code Review
MichaelGrafnetter/DSInternals
Perform a systematic code review of all source files, focusing on security, performance, backwards compatibility, and design principles.
Release Preparation
MichaelGrafnetter/DSInternals
Prepare the DSInternals project for a new release by updating version numbers, release notes, and changelog.
Update Copyright Year
MichaelGrafnetter/DSInternals
Update copyright year references across the project at the beginning of each calendar year.
Related
Categories
Questions about Doc Comments
What does Doc Comments do?
Ensure that C and C++/CLI types are documented with XML comments and follow best practices for documentation. Doc Comments is an agent skill from MichaelGrafnetter/DSInternals. Ensure that C and C++/CLI types are documented with XML comments and follow best practices for documentation.
When should I use Doc Comments?
Doc Comments fits situations like: security work in your project.
How do I install Doc Comments in Claude Code?
Run `npx skills add MichaelGrafnetter/DSInternals --skill doc-comments -a claude-code`. Or copy the skill folder (.agents/skills/doc-comments in MichaelGrafnetter/DSInternals) into .claude/skills/doc-comments in your project. Claude Code loads it when a task matches its description.
How do I install Doc Comments in Codex?
Run `npx skills add MichaelGrafnetter/DSInternals --skill doc-comments -a codex`. Or copy the skill folder (.agents/skills/doc-comments in MichaelGrafnetter/DSInternals) into .agents/skills/doc-comments in your project. Codex loads it when a task matches its description.
Can I use Doc Comments 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 MichaelGrafnetter/DSInternals --skill doc-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-comments, .gemini/skills/doc-comments, .github/skills/doc-comments and .opencode/skills/doc-comments in your project.
What does Doc Comments need to run?
SKILL.md names no scripts, command-line tools or credentials: Doc Comments is instructions for the agent only.
Does Doc Comments access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Doc Comments 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 Doc Comments use?
Doc Comments is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Doc Comments use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Doc Comments?
Skills that share tags, products or a category with Doc Comments: Code Audit (3stoneBrother/code-audit, 893 stars), Constant Time Analysis (sickn33/agentic-awesome-skills, 47k stars), Fory Performance Optimization (apache/fory, 4.6k stars) and MCP Debugger (debugmcp/mcp-debugger, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Doc Comments?
MichaelGrafnetter (a GitHub user) maintains it in MichaelGrafnetter/DSInternals, which has 1,968 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 11, 2026.
Source: MichaelGrafnetter/DSInternals on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.