dotfiles

Analyze, group, and commit uncommitted changes as atomic conventional commits. Use this skill whenever the user says 'commit', 'commit this', 'commit these changes', 'commit my changes', 'smart commit', wants their diff split into logical commits, or asks to create a commit in any way. Always use this skill for committing — never run git commit directly.

Audit Claude Code configuration for security: check permissions, hooks, MCP servers, and settings

Create or update today's daily note at `~/knowledge/notes/journal/YYYY/MM-MMM/YYYY-MM-DD-DayName.md`, appending or replacing a session entry under `## Agent Summary`. Use when the user asks to update the daily note, log a session, append to the journal, or when invoked by the session-history hook after a session summary is written.

Edit config files inside the stow-based dotfiles repo and re-stow them with `make link`. Use this skill whenever the user asks to modify, add, or tweak any config under `$HOME` that lives in dotfiles — `.zshrc`, `.zshenv`, `.zprofile`, anything under `.config/`, `.local/`, `.claude/`, `.kiro/`, `.meshclaw/`, `.aws/`, `.unison/`, the `Makefile`, or any other tracked dotfile. Trigger even if the user phrases it as "change my config", "update my zshrc", "add this to claude settings", "tweak my tmux config", "modify my aliases", etc. — direct edits to `$HOME` are wrong because they bypass version control and get clobbered by the next `make link`.

Summarize unread emails via Outlook MCP, group by priority, draft replies

Audit IAM policies in CDK/CloudFormation/Terraform for least-privilege violations

Automatic security scanning on every code change with CWE/OWASP mapping

Pre-merge security audit with CWE/OWASP mapping

Summarize unread Slack threads from key channels, highlight action items

Launch a TDD agent team pipeline — coordinates test-writer, test-reviewer, code-writer, code-reviewer, and validator teammates through RED→GREEN→REFACTOR cycles with quality gates. Manual-invocation only via /tdd-team <spec-path>. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.

Generate threat models using STRIDE methodology

Store important information, decisions, implementations, or learnings to the knowledge base. Use when preserving context, decisions, debugging solutions, or implementation details for future reference.

Create implementation plans with requirements, design, and tasks. Use when planning new features or components. Generates three files with approval gates at each phase.

Generate comprehensive work summaries from daily notes or conversation context. Use for performance reviews, project retrospectives, or documenting completed work with timeline and impact.

Create clear, effective engineering design documents following structured templates. Use when writing technical design docs for software implementations with problem statement, solution, and alternatives.

Store important information, decisions, implementations, or learnings to the knowledge base. Use when preserving context, decisions, debugging solutions, or implementation details for future reference.

Create implementation plans with requirements, design, and tasks. Use when planning new features or components. Generates three files with approval gates at each phase.

Generate comprehensive work summaries from daily notes or conversation context. Use for performance reviews, project retrospectives, or documenting completed work with timeline and impact.

Generate foundational steering documents (product.md, tech.md, structure.md) for current workspace by analyzing codebase. Use when starting new projects or documenting existing ones.

Sync existing steering documents from workspace .gemini/steering/ to knowledge base with Context sections. Use when steering docs already exist and need syncing to knowledge base.

Generate foundational steering documents (product.md, tech.md, structure.md) for current workspace by analyzing codebase. Use when starting new projects or documenting existing ones.

Sync existing steering documents from workspace .kiro/steering/ to knowledge base with Context sections. Use when steering docs already exist and need syncing to knowledge base.