claude-code-companion
Use this skill when the user wants a Claude Code-native companion workflow rather than a one-off command.
Best fit
Reach for claude-code-companion when the user wants one or more of these outcomes:
- break a Claude Code task into review-first, implementation, and verification stages
- continue a prior Claude Code effort without overpromising hidden persistent threads
- coordinate bounded follow-up work after an earlier review or diagnosis
- decide when work should stay in the foreground versus be structured as a follow-up process
- standardize how Claude Code handles multi-step task continuation inside the current repository
Positioning
| Skill | Best for |
|---|---|
claude-code-companion |
Companion-style orchestration inside Claude Code itself |
codex-companion |
Codex-specific background jobs, resumable Codex task threads, and runtime lifecycle commands |
| direct Claude Code usage | Simple one-shot reads, edits, tests, and short implementation loops |
More from bahayonghang/my-claude-code-settings
tech-design-doc
Generate technical design documents with proper structure, diagrams, and implementation details. Use when designing a new feature, documenting architecture decisions, or planning refactoring work. Default language is English.
105bidwriter
智能标书编写专家，专精工程咨询、建筑设计、市政工程领域的投标文件编写。
68article-cover
Generate article cover images as SVG. Use when creating cover/banner/header graphics for blogs, documentation, social media cards, or OG images. Trigger this skill whenever the user mentions article covers, blog banners, post thumbnails, social sharing images, or any visual header for written content — even if they don't explicitly say 'SVG'. Do not use it for full-scene illustrations, photo editing, or slide theme work.
63tech-blog
Write technical blog posts with source code analysis OR doc-driven research. Use when user wants to explain system internals, architecture, implementation details, or technical concepts with citations.
53git-commit-cn
Safely orchestrate Chinese Conventional Commits for staged Git changes, or for all working-tree changes when the user explicitly asks to include everything. Use when the user asks to write a commit message, split staged changes, split all changes, commit everything regardless of stage state, include untracked files in the commit set, organize a messy index before committing, prepare a Chinese commit, draft a Conventional Commit, or generate structured commit text without pushing by default.
47gemini-image
>-
46