thkt/checkout
skills/checkout/SKILL.md
Analyze Git changes and create a new branch with an appropriate name.
$ install --global
skillsauthnpx skillsauth add thkt/dotclaude checkoutInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 15, 2026, 2:50 AM343.9s1 file scanned
SKILL.md
- name:
- checkout
- description:
- Analyze Git changes and create a new branch with an appropriate name.
- when_to_use:
- ブランチ作成, ブランチ切って, ブランチ名, branch name
- allowed-tools:
- Bash(git:*) AskUserQuestion
- model:
- haiku
- argument-hint:
- [context or ticket number]
/checkout - Git Branch Creation
Input
$ARGUMENTS may contain context or a ticket number. Trim whitespace; if empty, analyze the Git changes alone. If non-empty, treat it as a hint for the branch name scope or ticket ID.
Execution
- Run
git statusandgit diffin parallel to read the changes - Generate 3 branch name candidates that follow the naming convention from the changes and
$ARGUMENTS - Present each candidate with a selection reason via
AskUserQuestionand let the user pick one - Create the new branch via
git checkout -b <selected name>
Branch Naming
Determine the type from the changes and assemble the branch name in this format. Each type's trigger is in the table below.
<type>/<scope>-<description>
<type>/<ticket>-<description>
| Prefix | Purpose | Trigger | | --------- | -------------------- | --------------------- | | feature/ | New functionality | New files, components | | fix/ | Bug fixes | Error corrections | | refactor/ | Code improvements | Restructuring | | docs/ | Documentation | .md files, README | | test/ | Test additions/fixes | Test files | | chore/ | Maintenance | Dependencies, config | | perf/ | Performance | Optimization, caching |
- Compose it from lowercase and hyphen separators; do not use spaces, underscores, or CamelCase
- Keep scope and description to 2-4 words and avoid vague words such as update
- If
$ARGUMENTShas a ticket ID, include it at the<ticket>position; do not include dates
Error Handling
| Error | Action | | ----------------- | --------------------------- | | No changes | Report there are no changes | | Branch exists | Suggest an alternative name | | No git repository | Report it is not a git repo |
Output
Report the created branch name on a single line.
Related Skills
thkt/use-cli-herdr
tools
VerifiedTrustedCommunity
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
11SKILL.mdUpdated Jul 27, 2026
thkt/scribe
development
VerifiedTrustedCommunity
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
11SKILL.mdUpdated Jul 20, 2026
thkt/dr
development
VerifiedTrustedCommunity
Create Decision Records (DR) in MADR v4 format with auto-numbering.
11SKILL.mdUpdated Jul 15, 2026
thkt/shake
development
VerifiedTrustedCommunity
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).
11SKILL.mdUpdated Jul 13, 2026