菜单
Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Automate browsers and apps with agent-browser. Use for testing, screenshots, forms, scraping, Browserbase/cloud browsers, and Electron when real Chrome cookies are not required.
Add authentication with Better Auth (TypeScript). Use for email/password, OAuth providers (Google, GitHub), 2FA/MFA, passkeys/WebAuthn, sessions, RBAC, rate limiting.
Target a real Google Chrome profile for browser automation through Chrome DevTools MCP or claude-in-chrome. Provides a chrome-profile CLI, profile discovery, bridge diagnostics, setup playbooks, and the URL-anchor workflow for selecting the correct profile tab.
Review code quality with evidence-based rigor. Supports input modes: pending changes, PR number, commit hash, and codebase scan. Focuses on bugs, regressions, maintainability, reliability, and verification gaps.
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues, call stack tracing, multi-layer validation, log analysis, CI/CD failures, database diagnostics, system investigation.
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
| name | ck:docs |
| description | Analyze codebase and manage project documentation. Use for doc initialization, updates, summaries, codebase analysis. |
| user-invocable | true |
| when_to_use | Invoke to create, refresh, or audit project documentation. |
| category | utilities |
| keywords | ["documentation","init","update","summarize"] |
| argument-hint | init|update|summarize |
| metadata | {"author":"claudekit","version":"1.2.0"} |
Analyze codebase and manage project documentation through scouting, analysis, and structured doc generation.
IMPORTANT: Invoke "/ck:project-organization" skill to organize the outputs.
If invoked without arguments, use AskUserQuestion to present available documentation operations:
| Operation | Description |
|---|---|
init | Analyze codebase & create initial docs |
update | Analyze changes & update docs |
summarize | Quick codebase summary |
Present as options via AskUserQuestion with header "Documentation Operation", question "What would you like to do?".
| Subcommand | Reference | Purpose |
|---|---|---|
/ck:docs init | references/init-workflow.md | Analyze codebase and create initial documentation |
/ck:docs update | references/update-workflow.md | Analyze codebase and update existing documentation |
/ck:docs summarize | references/summarize-workflow.md | Quick analysis and update of codebase summary |
Parse $ARGUMENTS first word:
init → Load references/init-workflow.mdupdate → Load references/update-workflow.mdsummarize → Load references/summarize-workflow.mdinit)Documentation lives in ./docs directory:
./docs
├── project-overview-pdr.md
├── code-standards.md
├── codebase-summary.md
├── design-guidelines.md
├── deployment-guide.md
├── system-architecture.md
└── project-roadmap.md
Use docs/ directory as the source of truth for documentation.
When authoring or refreshing diagrams in system-architecture.md, apply the universal SVG layout rules from /ck:tech-graph's references/svg-layout-best-practices.md (component spacing, arrow routing, label placement, z-index ordering). Pair with /ck:preview --diagram for visual self-review, or use /ck:tech-graph directly for publish-grade output.
IMPORTANT: Do not start implementing code.