dotfiles

Read third-party package source code via the `opensrc` CLI when investigating internal implementations of dependencies. ALWAYS invoke this skill before reading library/package source — including phrasings like "how does <pkg> work internally", "I want to read the source of <pkg>", "investigate the implementation of <pkg>", "let me check what <pkg> does under the hood", "git clone <repo> to read it", "look inside <pkg>", "<pkg> の実装を確認したい", "<pkg> のソースコードを調査", "<pkg> の中身を見たい", or any task that requires reading code from an npm / PyPI / crates.io package or a public GitHub/GitLab/Bitbucket repo. Use this skill instead of `git clone`, instead of asking the user to paste source, and instead of guessing from memory. Also use it when fetching only the path matters, e.g. setting up a search target for `rg` / `find` / `cat` across a dependency.

Enforce uncompromising implementation standards — no ad-hoc fixes, no shortcuts, no scope reduction. Use this skill whenever the user invokes /rigorous before giving an implementation task. This skill sets the mindset for the entire task: always pursue the architecturally correct solution regardless of change volume or complexity. Also use when the user says things like "ちゃんとやって", "しっかり実装して", "妥協しないで", "手を抜かないで", or any indication they want rigorous, no-compromise implementation.

Create a git commit for work done in the current session. Use this skill whenever the user invokes /commit or asks to commit their changes. This skill handles file selection (session-changed files, staged files, or explicitly specified files), commit message generation based on the repository's existing style, and outputs a summary of the commit. MUST be used for any commit operation — never commit without following this workflow.

Autonomous work mode — the user is going to sleep or will be unavailable, and cannot respond to questions or confirmations during the task. This skill is invoked explicitly via /sleep only. Do not auto-trigger based on conversational cues. Use this skill alongside whatever other skills the task requires.

Fetch the latest CLAUDE.md best practices from the official documentation. Use this skill before creating, updating, reviewing, or improving any CLAUDE.md file. Trigger on requests like "I want to write a CLAUDE.md", "review my CLAUDE.md", "what are the CLAUDE.md best practices?", or any work involving CLAUDE.md files.

Review the current session's work and evaluate whether any CLAUDE.md / AGENTS.md files in the project need updating. Only update when genuinely necessary. Use at the end of a session or at a natural breakpoint. Trigger when the user invokes /session-recap, or says things like "review docs", "do CLAUDE.md files need updating?", "reflect on what we did", "recap the session", or wants to check documentation consistency after completing work. This is not a mechanical codebase scan — it evaluates update needs based on the context of what was done during the session.

Scan the codebase to identify refactoring candidates — code that works correctly but would benefit from structural improvement. Use this skill when the user asks to find refactoring targets, code smells, cleanup opportunities, structural improvements, or wants to improve code maintainability. Also use when the user says things like "what should we clean up", "find messy code", "technical debt scan", or "what needs refactoring". This is NOT for bug hunting or security audits — it focuses purely on code structure, readability, and maintainability.

Synchronize CLAUDE.md and AGENTS.md files with the actual codebase state. Use this skill when the user invokes /sync-agents-md, asks to sync documentation, or wants to check if CLAUDE.md/AGENTS.md are up to date with the codebase. This skill compares documented claims (file paths, commands, tool names, directory structures, workflows) against reality and fixes inaccuracies. It only corrects what's wrong — it does not add new sections or expand documentation beyond what already exists.

Question-only mode — investigate and explain without making any changes. Use this skill when the user invokes /ask, meaning they want to understand something (code behavior, architecture, configuration, errors, concepts) without any files being modified. This skill MUST be used whenever the user types /ask, even if the question seems simple. The user is explicitly signaling "I'm asking a question, not requesting work."