Skip to content

NagareNegishi/Job-Application-Tracker / .claude/skills/code-commenting

code-commenting

Verified

Apply whenever writing or editing code in any language, even if comments are not explicitly requested. Enforces comment and documentation discipline: concise file headers, function docs in the language's native format, inline comments for non-obvious logic, and protection of existing comments. Not required during suggestion-only or discussion when no file is written.

Code Commenting

Governs comments and documentation only. Does not change how the code itself is written.

Documentation format

Use the language's native doc-comment convention. Examples:

  • C# → XML doc (///)
  • Java → Javadoc (/** */)
  • Python → docstrings
  • JavaScript / TypeScript → JSDoc / TSDoc
  • Go → doc comments (// Name ...)
  • Rust → ///

For any other language, follow that language's accepted documentation standard.

File header

Add a concise header at the top of every file stating what the file is in general, in one or two lines. No implementation detail; detail belongs to the functions.

Function comments

Document every function with a comment describing what it does, not how. Skip functions that are trivial, self-evident, or not conventionally documented (getters, setters, one-liners whose name already says everything).

Inline comments

Add inline comments only where logic is complex or a decision is non-obvious: anything a later reader needs to follow the code. Explain the reason or key point, not the mechanics.

Style

  • Concise but meaningful. Write for a human reader in natural language.
  • No filler, no line-by-line narration, no AI-tell phrasing.
  • Never add a comment that only states the obvious or adds nothing.

Existing comments (protected)

  • Do not modify, rewrite, or delete existing comments while coding.
  • Adding new comments is allowed freely.
  • To change or remove an existing comment, including obvious or no-value ones, ask permission first.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall