dotfiles

Aggregate today's Claude Code session logs and GitHub activity into a personal reflection-style daily report (what I did / what I was thinking / what I struggled with). Use whenever the user says '日報', 'daily report', '今日の振り返り', '今日何やった', '今日まとめて', or wants a self-reflective summary of a single day's development work. This is the right skill anytime the scope is a single day — even if the user doesn't say '日報' explicitly. Distinct from [[weekly-report]] (which covers a multi-day business week with aggregate stats); prefer daily-report for single-day scopes. Do NOT use for non-development journaling, sprint planning, or weekly/monthly reviews.

Create a GitHub Pull Request with auto-generated title and description. Use when user says 'PR作って', 'create PR', 'プルリクエスト', or wants to push and open a pull request. Do NOT use for reviewing existing PRs, merging PRs, or updating PR descriptions.

Summarize the learnings from the current Claude Code session and save them as a new Markdown note in the user's Obsidian vault at ~/Documents/Obsidian/SyncedNotes/. Use when the user explicitly asks to capture session insights to Obsidian — phrases like '今の学びをObsidianに保存して', 'この学びをまとめて', '学びをノートにして', 'Obsidianにメモして', 'save the learnings to Obsidian'. Extracts insights across debugging solutions, newly-encountered tech/tools/patterns, codebase-specific knowledge, and workflow improvements, then writes one consolidated note. Do NOT use for activity-style daily summaries (use [[daily-report]] instead), for appending to an existing note, or for non-learning content.

Generate and execute git commits with Conventional Commits format. Use when user says 'commit', 'コミットして', 'save changes', 'この変更をコミット', or has staged changes to commit. Do NOT use for amending existing commits, interactive rebase, or unstaging files.

Design an implementation plan and refine it through human annotation cycles. Use when user says '設計して', '計画を立てて', 'plan the implementation', 'how should I implement', or wants to plan before coding. Do NOT use for direct implementation, code review, or research without planning.

Run the full research → design → implement pipeline end-to-end. Use when user says '開発して', 'build this feature', '新機能を作って', '一気通貫で実装', or wants the complete workflow from investigation to implementation. Do NOT use for research-only, design-only, or implementing an existing plan — use /research, /design, or /implement respectively.

Execute an approved design plan step by step with validation and checklist tracking. Use when user says '実装して', 'implement this plan', 'design-*.mdを実装', or has an approved plan file ready for implementation. Do NOT use for planning, research, or implementing without a plan file.

Diagnose and fix failed GitHub Actions workflow runs. Use when user says 'CIが落ちた', 'fix CI', 'テストが通らない', 'ワークフローが失敗', or has a failing GitHub Actions run to debug. Do NOT use for local test failures unrelated to CI, setting up new workflows, or CI configuration questions.

Aggregate GitHub + Claude Code activity into a structured weekly review report. Use when user says '週報を作って', 'weekly report', '今週の振り返り', '活動レポート', or wants to review development activity for a period. Do NOT use for daily standups, sprint planning, or non-development activity tracking.

Deep codebase investigation producing structured research documents. Use when user says 'investigate', 'how does X work', '仕組みを教えて', 'コードを調査して', '既存実装を把握したい', or wants to understand existing code before planning. Do NOT use for simple file searches, quick questions about specific functions, or making code changes.