Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow.
Install Code Commenting Strategy
$ npx skills add kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kitchen-engineer42/pdf2skills code-commenting-strategy --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/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .claude/skills/code-commenting-strategy && 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 "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .claude/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategyType 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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kitchen-engineer42/pdf2skills code-commenting-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .agents/skills/code-commenting-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .agents/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kitchen-engineer42/pdf2skills code-commenting-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .cursor/skills/code-commenting-strategy && 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 "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .cursor/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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/kitchen-engineer42/pdf2skills.git --path 'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy'--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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kitchen-engineer42/pdf2skills code-commenting-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .gemini/skills/code-commenting-strategy && 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 "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .gemini/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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 kitchen-engineer42/pdf2skills code-commenting-strategyInstalls 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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .github/skills/code-commenting-strategy && 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 "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .github/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kitchen-engineer42/pdf2skills code-commenting-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy' .opencode/skills/code-commenting-strategy && 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 "code-commenting-strategy" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/code-commenting-strategy into .opencode/skills/code-commenting-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-commenting-strategy", 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
code-commenting-strategy- GitHub stars
- 134
- Token cost
- ~894 tokens
- SKILL.md length
- 328 words
- Files
- 2 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow.
- Works in 4 steps: Integrate Comments with Development… → Performance Considerations → Optimal Comment Density → …
- Establishing commenting standards
- SKILL.md covers When to Use This Skill, Core Principles, Decision Flow and Warning Signs
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Code Commenting Strategy is an agent skill from kitchen-engineer42/pdf2skills. Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow. Use when establishing commenting standards, addressing performance concerns, implementing Pseudocode Programming Process (PPP), or determining appropriate comment frequency.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/comment-density-research.md`).
It sits in Development. The repository describes itself as: Convert a book into skills directly callable to Claude Code.
When your agent uses it
- Establishing commenting standards
- Addressing performance concerns
- Implementing Pseudocode Programming Process (PPP)
- Determining appropriate comment frequency
Example prompts
- “/code-commenting-strategy”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Integrate Comments with Development Workflow
- Performance Considerations
- Optimal Comment Density
- Pseudocode Programming Process (PPP) Integration
What it can do on your machine
Read from SKILL.md and the folder at commit 0d70065. 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
Code Commenting Strategy loads about 894 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 328 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 328 words (~894 tokens).
“Write comments synchronously with code, not as a separate task.”
- name
- code-commenting-strategy
Files
SKILL.md and 1 other file (references) in skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy of kitchen-engineer42/pdf2skills.
- SKILL.md
- references/comment-density-research.md
Open the folder on GitHubat commit 0d70065
Compare with similar skills
Code Commenting Strategy 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 |
|---|---|---|---|---|---|---|
| Code Commenting Strategy this skillkitchen-engineer42/pdf2skills | 134 | — | ~894 | Automated safety check: Pass | None | |
| Vercel Composition Patternssupabase/supabase | 111k | 59 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
More from kitchen-engineer42/pdf2skills
All 21 skills in this repoSoftware Engineering Standards
kitchen-engineer42/pdf2skills
Reference and apply IEEE, ISO/IEC, and other software engineering standards for development, quality assurance, and project management.
Software Engineering Standards Reference
kitchen-engineer42/pdf2skills
A skill your agent uses when you need to reference, cite, or apply software engineering standards.
Complex Conditional Refactoring
kitchen-engineer42/pdf2skills
Refactor complex case statements and deeply nested code using appropriate strategies.
Pseudocode Programming Process
kitchen-engineer42/pdf2skills
A skill your agent uses when implementing complex logic, developing functions, or designing algorithms.
Class Organization And Layout
kitchen-engineer42/pdf2skills
Organize class members in standard order, separate classes with blank lines, and maintain one-class-per-file structure.
Code Commenting Checklists
kitchen-engineer42/pdf2skills
Use specific checklists to ensure comprehensive and high-quality code commenting for general code, data declarations, and program structures.
Related
Categories
Questions about Code Commenting Strategy
What does Code Commenting Strategy do?
Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow. Code Commenting Strategy is an agent skill from kitchen-engineer42/pdf2skills. Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow.
When should I use Code Commenting Strategy?
Code Commenting Strategy fits situations like: establishing commenting standards; addressing performance concerns; implementing Pseudocode Programming Process (PPP); determining appropriate comment frequency.
How do I install Code Commenting Strategy in Claude Code?
Run `npx skills add kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a claude-code`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy in kitchen-engineer42/pdf2skills) into .claude/skills/code-commenting-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Code Commenting Strategy in Codex?
Run `npx skills add kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a codex`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/code-commenting-strategy in kitchen-engineer42/pdf2skills) into .agents/skills/code-commenting-strategy in your project. Codex loads it when a task matches its description.
Can I use Code Commenting Strategy 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 kitchen-engineer42/pdf2skills --skill code-commenting-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-commenting-strategy, .gemini/skills/code-commenting-strategy, .github/skills/code-commenting-strategy and .opencode/skills/code-commenting-strategy in your project.
What does Code Commenting Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Commenting Strategy is instructions for the agent only.
Does Code Commenting Strategy 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 Code Commenting Strategy 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 Code Commenting Strategy use?
No licence was found for Code Commenting Strategy or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Code Commenting Strategy use?
About 894 tokens (SKILL.md is roughly 3.6k 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 427 tokens, read only when the agent opens those files.
What are the alternatives to Code Commenting Strategy?
Skills that share tags, products or a category with Code Commenting Strategy: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Commenting Strategy?
kitchen-engineer42 (a GitHub user) maintains it in kitchen-engineer42/pdf2skills, which has 134 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on February 24, 2026.
Source: kitchen-engineer42/pdf2skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.