メニュー
This skill should be used when the user asks to "commit changes", "create a PR", "push code", "check git status", or "review git history". Enforces safety checks and conventional commits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Control and inspect WezTerm terminal panes. Use when terminal interaction, command execution, reading terminal output, monitoring running processes, or working with existing shell sessions is required.
Invoke this skill when the user says "use btca"
This skill should be used when the user asks to "create a justfile", "write just recipes", "configure just settings", "add just modules", "use just attributes", "set up task automation", mentions justfile, just command runner, or task automation with just.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
Drizzle ORM for TypeScript - type-safe SQL queries, schema definitions, migrations, and relations. Use when building database layers in Next.js or Node.js applications.
This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from 'effect'. Also covers Effect + Next.js integration with @prb/effect-next.
| name | git-standards |
| description | This skill should be used when the user asks to "commit changes", "create a PR", "push code", "check git status", or "review git history". Enforces safety checks and conventional commits. |
<skill_doc>
Tool Enforcement:
Use the git_safe tool for all git operations (status, diff, log, add, commit, push).
Manual Agent Checks:
Before ANY commit, scan staged files using git_safe(action: "diff", target: "--cached") for:
.env, *_KEY, *_SECRET, password, token.dist/, node_modules/, .DS_Store.
Action: If found, UNSTAGE immediately and warn user.Format: <type>(<scope>): <description>
| Type | Meaning |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
refactor | Code change (no feature/fix) |
perf | Performance improvement |
test | Adding/fixing tests |
chore | Build/auxiliary tools |
Examples:
feat(auth): add google oauth providerfix(login): handle null session tokenTitle: Matches commit format. Body:
## Why
(Context/Problem)
## What
(Summary of changes)
## Verification
- [ ] Tests
- [ ] Manual Check
</skill_doc>