All authors
Claude Skills by atman-33
github.com/atman-3395 skills1 installs147 views
- Handoff GoWrite a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and paste-ready fallbacks when no multiplexer is in use.Votes: 0GitHub stars: 3
- HandoffCompact the current conversation into a handoff document for another agent to pick up.Votes: 0GitHub stars: 3
- HerdrControl herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).Votes: 0GitHub stars: 3
- Launch TeamLaunch a role-based team of Claude Code agents in separate multiplexer panes that coordinate on one task by messaging each other directly.Votes: 0GitHub stars: 3
- Setup HerdrInstall herdr (terminal-native agent multiplexer), set up its Claude Code and OpenCode integrations, and configure shell profiles to auto-launch herdr on startup (replacing any existing Zellij autostart block). Use when the user wants to install or configure herdr.Votes: 0GitHub stars: 3
- Setup ZellijInstall Zellij and configure shell profiles to auto-launch Zellij on startup (replacing any existing herdr autostart block). Use when the user wants to install or configure Zellij's shell autostart.Votes: 0GitHub stars: 3
- Sidekick GoUse when the user explicitly asks to delegate work to a persistent sidekick/helper agent in its own pane that you can iterate with across multiple rounds (e.g. review -> fix -> re-review) without losing its context each time, or when another skill's instructions explicitly direct invoking sidekick-go. Do not use for a one-off review or one-shot subagent task; that's the Agent/Task tool's job.Votes: 0GitHub stars: 3
- Wsl Vscode DoctorDiagnose and fix `code .` failing to launch, or opening a disconnected Windows-side VS Code instead of a WSL-connected (Remote-WSL) window, in a herdr-spawned WSL shell.Votes: 0GitHub stars: 3
- Create Claude MdGenerate or refine a concise, effective CLAUDE.md for the current project following official best-practice guidelines. Use when the user wants to create, write, or update a project's CLAUDE.md.Votes: 0GitHub stars: 3
- Create ReadmeCreate a comprehensive, well-structured README.md for the current project. Use when the user wants to create, write, or refine a project's README.Votes: 0GitHub stars: 3
- Create Release NotesWrite user-facing release notes from the Conventional Commits history between two refs — grouped by impact, in plain language, with internal-only changes filtered out. Use when the user wants release notes, an announcement of what's new in a version, or a user-readable summary of changes since the last release (distinct from a developer changelog).Votes: 0GitHub stars: 3
- Create Work LogCompose a daily or weekly work log from git activity across the user's configured repositories and save it as Markdown (e.g. into an Obsidian vault). Use when the user asks for a work log, daily report, weekly summary, 日報/週報, or "what did I do today/this week".Votes: 0GitHub stars: 3
- Post To SlackPost a message to a Slack channel, resolving channel/user names to IDs and adding an optional @mention or thread reply. Use when the user wants to post, share, or notify something in Slack, or when another skill needs to deliver its output to a Slack channel.Votes: 0GitHub stars: 3
- Create Claude CommandUse when building or improving a Claude Code slash command in a project's own `.claude/commands/`: $ARGUMENTS handling, file/bash injection, agent invocation, multi-agent orchestration, or command naming.Votes: 0GitHub stars: 3
- Install SkillInstall a Claude Code skill from a GitHub skills repository URL.Votes: 0GitHub stars: 3
- Manage Desktop RoutinesCreate, back up, and restore Claude Code Desktop local routines (scheduled tasks) so they survive a PC change. Use when the user wants to set up a recurring or one-off Desktop routine, back up their routines, or restore routines on a new machine.Votes: 0GitHub stars: 3
- Capture RuleCapture a reusable, non-obvious project insight into the rules home where it will auto-inject in future sessions. Use when investigation or implementation surfaces knowledge worth persisting (a gotcha, a convention, the "why" behind a decision), or when the user asks to remember a project learning.Votes: 0GitHub stars: 3
- Commit ChangesCommit the current changes with a Conventional Commits message. Use when the user asks to commit, or when a workflow reaches its commit step after implementation is verified.Votes: 0GitHub stars: 3
- Create AdrRecord an architecture/design decision as an ADR (Architecture Decision Record) in the target repository's docs/adr/. Use when the user wants to document a design decision, its alternatives and consequences, or says "record this decision" / "write an ADR".Votes: 0GitHub stars: 3
- Create Feature BranchCreates a new work branch from main inside the intended repository after confirming the branch target and repository context, named <type>/<task-id>-<slug> unless the repository says otherwise. Use when the user wants to start a new branch, asks to create a branch for upcoming work, mentions a branch name such as feature/<name> or fix/<name>, or another workflow has already resolved the target repository.Votes: 0GitHub stars: 3
- Create Manual Test GuideGenerate a self-contained HTML manual-testing guide for an implemented change — environment setup, a visual test-flow diagram, step-by-step scenarios with expected results, and interactive pass/fail checkboxes with a Markdown results export. Use when the user wants to verify an implementation by hand, asks "how do I test this", or wants a verification document for a feature/branch/PR.Votes: 0GitHub stars: 3
- Create Onboarding GuideGenerate a self-contained HTML onboarding tour of a repository — architecture diagram, directory map, key flow walkthroughs, and a recommended reading order — for new team members. Use when the user wants onboarding material, asks for a codebase overview/architecture tour, or wants to explain a repo to someone new.Votes: 0GitHub stars: 3
- Create Pull RequestAnalyzes git changes, drafts localized PR titles and bodies, and assists with creating or updating GitHub pull requests for the active target project repository. Use when working from the harness workspace (e.g. the workhub vault) and the user wants to create a PR, review branch changes, draft or update a PR description, or check whether a branch is ready for review.Votes: 0GitHub stars: 3
- Create Review GuideGenerate a self-contained HTML code-review guide for the current changes — big-picture overview, architecture diagram of affected modules, a file/class responsibility map, and an annotated change walkthrough — so a reviewer can grasp the whole implementation before diving into the diff. Use when the user wants review material for a branch/PR, asks to "explain the changes for review", or wants a visual summary of what was implemented where.Votes: 0GitHub stars: 3
- Investigate Bug ReportInvestigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".Votes: 0GitHub stars: 3
- Setup AllRun all project setup steps in sequence — scaffold project-context.json and set up rules-ex infrastructure.Votes: 0GitHub stars: 3
- Setup Project ContextScaffold or show the .claude/project-context.json file that the workhub harness hooks read to inject project context, target-repo guidance, and optional post-edit format commands.Votes: 0GitHub stars: 3
- Setup Rules ExScaffold the rules-ex extended-rules infrastructure (.claude/rules/rules-ex-authoring.md and .claude/rules-ex/README.md) required by the workhub plugin's inject-extended-rules hook.Votes: 0GitHub stars: 3
- Persona Commit簡潔なコミットメッセージを生成する。Conventional Commits、件名50文字以内、「何を」より「なぜ」。 「コミットメッセージ作って」「/persona-commit」で起動。Votes: 0GitHub stars: 3
- Persona Compress自然言語のメモリファイル（CLAUDE.md、todo、設定メモ）を圧縮して入力トークンを削減する。 コード・URL・パス・構造は完全保持。「/persona-compress <path>」「メモリファイル圧縮」で起動。Votes: 0GitHub stars: 3
- Persona Helppersona プラグインの全コマンド・レベル・キャラクター追加手順のリファレンスカード。 1回限りの表示で状態は変えない。「/persona-help」で起動。Votes: 0GitHub stars: 3
- Persona New新しいペルソナのキャラクターを作成する。テンプレートから character.md を起こし、 ユーザー層に保存する。「キャラクターを追加」「/persona-new」で起動。Votes: 0GitHub stars: 3
- Persona Review簡潔な PR レビューコメントを生成する。1行1指摘、位置・問題・修正、重大度タグ付き。 「PRレビューして」「コードレビュー」「/persona-review」で起動。Votes: 0GitHub stars: 3
- Persona Stats現セッションの実トークン使用量と推定削減量を表示する。セッションログから直接読み取る。 「/persona-stats」で起動。Votes: 0GitHub stars: 3
- Persona応答口調のキャラクターを切り替える。キャラクター一覧の表示、切替、レベル変更、解除。 「ペルソナ」「キャラクター変更」「口調を変えて」「/persona」で起動。Votes: 0GitHub stars: 3
- Opencode Log InvestigationInvestigates OpenCode runtime errors by locating and analyzing log files. Use when OpenCode fails to start, plugins do not load, MCP servers error out, or terminal shows cryptic errors without details.Votes: 0GitHub stars: 3
- React Router V7 AppImplements React Router v7 app structure, routing patterns, and component templates. Use when creating or modifying React Router v7 applications to ensure consistent folder structure, data loading patterns, and component architecture.Votes: 0GitHub stars: 3
- Strategy DecomposeDecompose a strategy handed down from above into a hierarchy of aspects and states, audit it for necessity, sufficiency and overlap, and output it as an xlsx. Use before writing your own team's or unit's policy from a company/department/team strategy, when the user wants to break a strategy down into "what state we need to reach", or asks to check whether a decomposition is MECE.Votes: 0GitHub stars: 3
- Load Project ContextPrime a session with a team project's current state - backlog, sprint, repo progress - and refresh its _index.md summary. Use when the user asks "where are we" on a team project, or at the start of a work session on one.Votes: 0GitHub stars: 3
- Manage BacklogAdd, refine, split, or reorder PBIs in the file-based product backlog in the team-shared folder. Use when the user wants to create backlog items, write user stories or acceptance criteria, estimate points, split oversized items, or tidy the product backlog.Votes: 0GitHub stars: 3
- Plan SprintPlan a sprint - set the goal, commit backlog items into scope, and write the burndown baseline (scope.json). Use at a sprint boundary when the user wants to plan the next sprint or commit items to a sprint.Votes: 0GitHub stars: 3
- Report Daily ProgressGenerate the daily progress report - PBI status board, burndown chart, and merges of the day - as a self-contained HTML file in the team-shared folder. Use in the daily routine, or when the user asks for today's progress report or a burndown chart.Votes: 0GitHub stars: 3
- Review SprintWrite the sprint review - scope vs done, demo pointers, and carry-over decisions. Use at sprint end when the user wants a sprint review, sprint summary, or to close out a sprint.Votes: 0GitHub stars: 3
- Setup Team ContextSet up team-ops for this machine/project - create .claude/team-context.json, scaffold the team-shared ai/ folder skeleton, and optionally register a project. Use when onboarding a machine to a team shared folder, when the team-context hook reports a config error, or when adding a new team project.Votes: 0GitHub stars: 3
- Start PbiStart work on a PBI - set it to doing and issue the convention-compliant work branch name (pbi/<id>-<slug>). Use when a developer picks up a backlog item, or asks which branch name to use for a PBI.Votes: 0GitHub stars: 3
- Team Kb IndexRebuild or repair the team knowledge base indexes (_index.md files) in the team-shared folder. Use after several notes were added or moved, when indexes look stale, or when team-kb-save reports a larger reshuffle is needed.Votes: 0GitHub stars: 3
- Team Kb QueryAnswer questions from the team-shared knowledge base. Use when the user asks about team rules, working agreements, domain knowledge, past decisions, or anything a teammate might have documented in the shared folder.Votes: 0GitHub stars: 3
- Team Kb SaveSave reusable team knowledge into the team-shared knowledge base. Use when this session surfaces a process gotcha, decision rationale, domain know-how, or team rule worth sharing with teammates, or when the user asks to save something to the team KB.Votes: 0GitHub stars: 3
- Team OnboardGenerate an onboarding briefing for a new team member from the team KB, project specs, and recent progress. Use when someone new joins the team or a project, or when the user asks for an onboarding guide / "explain this team to a newcomer".Votes: 0GitHub stars: 3
- Update SpecUpdate the project's living spec (docs/spec/spec.md) from PBI acceptance criteria and diffs newly merged into the dev-main branches. Use in the daily routine after repo sync, or when the user asks to bring the spec up to date with what is implemented.Votes: 0GitHub stars: 3