Diagram Design
cathrynlavery/diagram-design
Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.
Agent skill
Integrate Comments Into Development Workflow
A workflow for writing code comments concurrently with development to ensure accuracy and reduce rework.
Install Integrate Comments Into Development Workflow
$ npx skills add kitchen-engineer42/pdf2skills --skill integrate-comments-into-development-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kitchen-engineer42/pdf2skills integrate-comments-into-development-workflow --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/integrate-comments-into-development-workflow' .claude/skills/integrate-comments-into-development-workflow && 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 "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .claude/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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/integrate-comments-into-development-workflowType 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 integrate-comments-into-development-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kitchen-engineer42/pdf2skills integrate-comments-into-development-workflow --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/integrate-comments-into-development-workflow' .agents/skills/integrate-comments-into-development-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .agents/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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 integrate-comments-into-development-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kitchen-engineer42/pdf2skills integrate-comments-into-development-workflow --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/integrate-comments-into-development-workflow' .cursor/skills/integrate-comments-into-development-workflow && 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 "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .cursor/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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/integrate-comments-into-development-workflow'--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 integrate-comments-into-development-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kitchen-engineer42/pdf2skills integrate-comments-into-development-workflow --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/integrate-comments-into-development-workflow' .gemini/skills/integrate-comments-into-development-workflow && 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 "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .gemini/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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 integrate-comments-into-development-workflowInstalls 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 integrate-comments-into-development-workflow -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/integrate-comments-into-development-workflow' .github/skills/integrate-comments-into-development-workflow && 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 "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .github/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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 integrate-comments-into-development-workflow -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 integrate-comments-into-development-workflow --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/integrate-comments-into-development-workflow' .opencode/skills/integrate-comments-into-development-workflow && 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 "integrate-comments-into-development-workflow" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/integrate-comments-into-development-workflow into .opencode/skills/integrate-comments-into-development-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrate-comments-into-development-workflow", 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
integrate-comments-into-development-workflow- GitHub stars
- 134
- Token cost
- ~435 tokens
- SKILL.md length
- 204 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
A workflow for writing code comments concurrently with development to ensure accuracy and reduce rework.
- Works in 3 steps: Write Comments Concurrently → Handle Intense Focus Scenarios → Address Design Complexity
- Actively coding
- SKILL.md covers When to Use This Skill, Core Procedure, Why This Matters and Expected Outcome
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Integrate Comments Into Development Workflow is an agent skill from kitchen-engineer42/pdf2skills. A workflow for writing code comments concurrently with development to ensure accuracy and reduce rework. Use when actively coding, planning development tasks, or addressing code maintainability in ongoing software projects.
Its SKILL.md is about 440 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 Development, covering Technical documentation. The repository describes itself as: Convert a book into skills directly callable to Claude Code.
When your agent uses it
- Actively coding
- Planning development tasks
- Addressing code maintainability in ongoing software projects
Example prompts
- “/integrate-comments-into-development-workflow”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Write Comments Concurrently
- Handle Intense Focus Scenarios
- Address Design Complexity
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
Integrate Comments Into Development Workflow loads about 435 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 204 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 204 words (~435 tokens).
“If writing comments during coding interrupts your flow:”
- name
- integrate-comments-into-development-workflow
Files
Just SKILL.md in skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/integrate-comments-into-development-workflow of kitchen-engineer42/pdf2skills.
Open the folder on GitHubat commit 0d70065
Compare with similar skills
Integrate Comments Into Development Workflow 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 |
|---|---|---|---|---|---|---|
| Integrate Comments Into Development Workflow this skillkitchen-engineer42/pdf2skills | 134 | — | ~435 | Automated safety check: Pass | None | |
| Diagram Designcathrynlavery/diagram-design | 45k | 1 repos | ~7.5k | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Get API Docs with chubandrewyng/context-hub | 14k | 2 repos | ~775 | Automated safety check: Pass | MIT | |
| Doc SyncJetBrains/ideavim | 10k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Mailspring App ScreenshotsFoundry376/Mailspring | 18k | — | ~1.5k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Get API Docs with chub
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
Mailspring App Screenshots
Foundry376/Mailspring
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
Draw.io Diagram Studio
Agents365-ai/drawio-skill
Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.
More from kitchen-engineer42/pdf2skills
All 21 skills in this repoCode Commenting Strategy
kitchen-engineer42/pdf2skills
Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow.
Software 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.
Related
Categories
Questions about Integrate Comments Into Development Workflow
What does Integrate Comments Into Development Workflow do?
A workflow for writing code comments concurrently with development to ensure accuracy and reduce rework. Integrate Comments Into Development Workflow is an agent skill from kitchen-engineer42/pdf2skills. A workflow for writing code comments concurrently with development to ensure accuracy and reduce rework.
When should I use Integrate Comments Into Development Workflow?
Integrate Comments Into Development Workflow fits situations like: actively coding; planning development tasks; addressing code maintainability in ongoing software projects.
How do I install Integrate Comments Into Development Workflow in Claude Code?
Run `npx skills add kitchen-engineer42/pdf2skills --skill integrate-comments-into-development-workflow -a claude-code`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/integrate-comments-into-development-workflow in kitchen-engineer42/pdf2skills) into .claude/skills/integrate-comments-into-development-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Integrate Comments Into Development Workflow in Codex?
Run `npx skills add kitchen-engineer42/pdf2skills --skill integrate-comments-into-development-workflow -a codex`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/integrate-comments-into-development-workflow in kitchen-engineer42/pdf2skills) into .agents/skills/integrate-comments-into-development-workflow in your project. Codex loads it when a task matches its description.
Can I use Integrate Comments Into Development Workflow 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 integrate-comments-into-development-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integrate-comments-into-development-workflow, .gemini/skills/integrate-comments-into-development-workflow, .github/skills/integrate-comments-into-development-workflow and .opencode/skills/integrate-comments-into-development-workflow in your project.
What does Integrate Comments Into Development Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Integrate Comments Into Development Workflow is instructions for the agent only.
Does Integrate Comments Into Development Workflow 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 Integrate Comments Into Development Workflow 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 Integrate Comments Into Development Workflow use?
No licence was found for Integrate Comments Into Development Workflow or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Integrate Comments Into Development Workflow use?
About 435 tokens (SKILL.md is roughly 1.7k 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 Integrate Comments Into Development Workflow?
Skills that share tags, products or a category with Integrate Comments Into Development Workflow: Diagram Design (cathrynlavery/diagram-design, 45k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Integrate Comments Into Development Workflow?
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.