home/dot_agents/adapters/opencode/skills/code-documentation/SKILL.md
Guidelines for self-explanatory code and meaningful documentation. Activate when working with comments, docstrings, documentation, code clarity, API documentation, JSDoc, or discussing code commenting strategies. Guides on why over what, anti-patterns, decision frameworks, and language-specific examples.
npx skillsauth add salverius-tech/dotfiles code-documentationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read ~/.agents/skills/code-documentation/knowledge.md for the full guidelines. Note: the path is ~/.agents, not ~/.claude.
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
testing
Guidelines for optimizing Claude rulesets and instruction files (CLAUDE.md, settings.json) using context efficiency principles. Includes strategies for skill extraction, progressive disclosure, token savings calculation, and deduplication. Manually invoke when optimizing rulesets, reducing context size, extracting content to skills, or improving ruleset organization.
tools
Activate when user needs multi-URL scraping, browser automation pipelines, or efficient tool orchestration to reduce API round-trips and context usage.
development
# Cross-Platform Hooks and Status Scripts Guidelines for writing Claude Code hooks and status scripts that work on Windows (PowerShell, Git Bash), WSL, and Linux. ## Activation Activate when: - Creating or modifying files in `.claude/hooks/` - Creating or modifying `.claude/claude-status` - Writing shell scripts that will run in Claude Code context - Debugging hook execution failures ## Critical Rules ### 1. Shebang Lines **Bash scripts**: Always use `#!/usr/bin/env bash` (NOT `#!/bin/bash