dotfiles

any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.

Review design specs for correctness, completeness, consistency, quality, implementability, and risks. Verifies claims against source code. Invoke with /review-spec <path-to-spec>.

Graphite CLI (gt) patterns for managing stacked pull requests. Use whenever the user mentions graphite, the `gt` command, PR stacks, or stacked diffs. Also triggers when starting development work in a repository where graphite is initialized (`.git/refs/graphite` exists or `gt` commands have been used). Invoke proactively when the user is creating branches, submitting PRs, or navigating between related branches in a collaborative repo — even if they don't mention graphite by name.

Use when creating issues, reviewing unestimated backlog items, or asked to estimate effort. Encodes the fibonacci scale and drives session/agent planning decisions.

Complete a development ticket end-to-end: root-cause any test failures, run the full test suite, lint and typecheck, commit, fast-forward merge to main, update the issue tracker to Done, and file follow-up issues for gaps. Invoke with /finish-ticket <ISSUE-ID>.

Session start check for MCP auth, git state, and worktree environment. Run at the start of any session involving MCP servers to surface expired tokens and env drift before they interrupt real work.

Technical documentation standards for both writing and reviewing. Use when creating new documentation, writing ADRs, drafting technical specs, reviewing existing docs for quality, or critiquing technical writing. Triggers on any documentation task, whether creating, editing, or reviewing.

Code review standards for quality, security, and maintainability. Use when reviewing code changes, analyzing PRs, auditing code quality, or when asked to review, critique, or assess code. Triggers on any code review, PR analysis, or code quality assessment task.

Atlassian Confluence integration via MCP. Use when working with Confluence wiki pages, spaces, documentation, or content management. Supports searching, reading, creating, updating pages, comments, and Jira linking. Triggers when the user mentions Confluence, wiki pages, or knowledge base content.

GitHub CLI (gh) patterns for PR review, issue management, and repository context. Use whenever working with pull requests, reviewing PRs, checking CI/CD status, analyzing commits, viewing GitHub issues, or when the user provides a GitHub URL or PR number. Triggers on any gh command usage, PR review workflow, or GitHub repository interaction.

Atlassian Jira integration via MCP. Use when working with Jira issues, tickets, epics, sprints, or project management. Supports searching, creating, updating issues, transitions, comments, and linking. Triggers when the user mentions Jira, tickets, issues, or project tracking.

Node.js and TypeScript development standards including project structure, quality tools (npm, Biome, Vitest, TypeScript), testing patterns, and best practices. Use whenever working in a project with package.json, tsconfig.json, or Node.js/TypeScript source files. Triggers on JavaScript, TypeScript, npm, or Node.js development tasks.

Python development standards including project structure, quality tools (uv, ruff, mypy, pytest), testing patterns, and best practices. Use whenever working in a project with pyproject.toml, setup.py, requirements.txt, or Python source files. Triggers on Python development, testing, linting, or packaging tasks.

File creation and modification standards. Use whenever creating new files, editing existing files, or writing content to disk. Requires using Write, Edit, or MultiEdit tools instead of bash commands like echo, cat with heredoc, or sed. Triggers on any file creation or modification task.

Analyze changes and create atomic git commits following conventional commit standards. Detects multiple logical changes and suggests splitting into separate commits.