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.
Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality.
Install Self Documenting Code Practices
$ npx skills add kitchen-engineer42/pdf2skills --skill self-documenting-code-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kitchen-engineer42/pdf2skills self-documenting-code-practices --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/self-documenting-code-practices' .claude/skills/self-documenting-code-practices && 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 "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .claude/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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/self-documenting-code-practicesType 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 self-documenting-code-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kitchen-engineer42/pdf2skills self-documenting-code-practices --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/self-documenting-code-practices' .agents/skills/self-documenting-code-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .agents/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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 self-documenting-code-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kitchen-engineer42/pdf2skills self-documenting-code-practices --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/self-documenting-code-practices' .cursor/skills/self-documenting-code-practices && 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 "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .cursor/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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/self-documenting-code-practices'--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 self-documenting-code-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kitchen-engineer42/pdf2skills self-documenting-code-practices --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/self-documenting-code-practices' .gemini/skills/self-documenting-code-practices && 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 "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .gemini/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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 self-documenting-code-practicesInstalls 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 self-documenting-code-practices -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/self-documenting-code-practices' .github/skills/self-documenting-code-practices && 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 "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .github/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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 self-documenting-code-practices -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 self-documenting-code-practices --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/self-documenting-code-practices' .opencode/skills/self-documenting-code-practices && 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 "self-documenting-code-practices" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/self-documenting-code-practices into .opencode/skills/self-documenting-code-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "self-documenting-code-practices", 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
self-documenting-code-practices- GitHub stars
- 134
- Token cost
- ~719 tokens
- SKILL.md length
- 320 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality.
- Works in 5 steps: Abstraction consistency: Does the class… → Naming accuracy: Is the class… → Interface intuitiveness: Does the class… → …
- Conducting code reviews
- SKILL.md covers Documentation Types, Programming Style as Primary…, Self-Documenting Code… and Result
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Self Documenting Code Practices is an agent skill from kitchen-engineer42/pdf2skills. Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality. Use when writing code, conducting code reviews, designing class interfaces, or establishing documentation standards.
Its SKILL.md is about 720 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 Code review. The repository describes itself as: Convert a book into skills directly callable to Claude Code.
When your agent uses it
- Conducting code reviews
- Designing class interfaces
- Establishing documentation standards
Example prompts
- “/self-documenting-code-practices”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Abstraction consistency: Does the class interface present a consistent abstraction?
- Naming accuracy: Is the class well-named, describing its core purpose?
- Interface intuitiveness: Does the class interface clearly indicate how to use it?
- Abstraction level: Is the interface abstract enough that users don't need to consider implementation details?
- Black-box property: Can the class be treated as a black box?
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
Self Documenting Code Practices loads about 719 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 320 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 320 words (~719 tokens).
“Apply these practices to create code that documents itself through quality design and style.”
- name
- self-documenting-code-practices
Files
Just SKILL.md in skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/self-documenting-code-practices of kitchen-engineer42/pdf2skills.
Open the folder on GitHubat commit 0d70065
Compare with similar skills
Self Documenting Code Practices 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 |
|---|---|---|---|---|---|---|
| Self Documenting Code Practices this skillkitchen-engineer42/pdf2skills | 134 | — | ~719 | Automated safety check: Pass | None | |
| 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 | |
| Backend Code Reviewlangflow-ai/langflow | 156k | — | ~3.5k | Automated safety check: Notes | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Mole Bug Patternstw93/Mole | 69k | — | ~2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
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.
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
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 Self Documenting Code Practices
What does Self Documenting Code Practices do?
Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality. Self Documenting Code Practices is an agent skill from kitchen-engineer42/pdf2skills. Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality.
When should I use Self Documenting Code Practices?
Self Documenting Code Practices fits situations like: conducting code reviews; designing class interfaces; establishing documentation standards.
How do I install Self Documenting Code Practices in Claude Code?
Run `npx skills add kitchen-engineer42/pdf2skills --skill self-documenting-code-practices -a claude-code`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/self-documenting-code-practices in kitchen-engineer42/pdf2skills) into .claude/skills/self-documenting-code-practices in your project. Claude Code loads it when a task matches its description.
How do I install Self Documenting Code Practices in Codex?
Run `npx skills add kitchen-engineer42/pdf2skills --skill self-documenting-code-practices -a codex`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/self-documenting-code-practices in kitchen-engineer42/pdf2skills) into .agents/skills/self-documenting-code-practices in your project. Codex loads it when a task matches its description.
Can I use Self Documenting Code Practices 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 self-documenting-code-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/self-documenting-code-practices, .gemini/skills/self-documenting-code-practices, .github/skills/self-documenting-code-practices and .opencode/skills/self-documenting-code-practices in your project.
What does Self Documenting Code Practices need to run?
SKILL.md names no scripts, command-line tools or credentials: Self Documenting Code Practices is instructions for the agent only.
Does Self Documenting Code Practices 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 Self Documenting Code Practices 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 Self Documenting Code Practices use?
No licence was found for Self Documenting Code Practices or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Self Documenting Code Practices use?
About 719 tokens (SKILL.md is roughly 2.9k 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 Self Documenting Code Practices?
Skills that share tags, products or a category with Self Documenting Code Practices: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Self Documenting Code Practices?
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.