メニュー
ALWAYS use this skill when committing code changes. Creates commits following conventional commit format. Trigger on any commit, git commit, save changes, or commit message task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Sysbench OLTP and TPC-H OLAP benchmark execution patterns, multi-instance PostgreSQL management, snapshot management, the full WorkloadOrchestrator pipeline, and performance measurement workflows. Use this skill when working on benchmark executors, evaluation pipeline, instance management, snapshot restoration, configuration application, restart policy, system metrics collection, or any code in src/benchmarks/, src/tuners/engine/, src/utils/applicator.py, or src/utils/environments/.
Complete codebase map for the PBT PostgreSQL tuning research project. Covers all source packages, file inventory with responsibilities, dependency relationships, data flow through the tuning pipeline, and navigation guide. Use this skill whenever you need to understand where code lives, how packages relate to each other, which file to modify for a given task, or when onboarding to the project. This is the first skill to consult when starting any new task in this repository.
Population-Based Training algorithm implementation patterns, evolutionary optimization conventions, and PBT-specific coding standards for the database tuning research project. Use this skill whenever working on PBT core logic, evolution, worker management, population management, scoring, normalization, convergence detection, exploit-explore mechanics, or any code in src/tuners/pbt/.
PostgreSQL configuration parameter (knob) tuning patterns, including parameter contexts (postmaster/sighup/user), knob space management, hardware-aware fractional normalization, safe bounds enforcement, and the knob tier system. Use this skill whenever working on knob configuration, parameter application, knob metadata, hardware-aware normalization, transfer learning via warm-start, or any code in src/knobs/, or src/utils/applicator.py.
Patterns for designing, executing, and analyzing reproducible scientific experiments in the database tuning domain. Covers multi-seed runs, baseline comparisons, BO comparisons, statistical reporting, and results directory structure. Use this skill when creating experiment scripts, setting up baselines, running multi-seed campaigns, comparing against Bayesian Optimization, computing improvement percentages, designing experiment protocols, or working on any experiment orchestration code.
Feature-driven scoring pipeline (scoring-v2) including the CompositeScorer, QuantileUtilityNormalizer, FeatureDrivenWeightModel, scoring policies (fixed_v1, feature_driven_v2), workload feature extraction, reliability gating, drift detection, and saturation expansion. Use this skill whenever working on score computation, metric normalization, metric weighting, scoring policies, workload features, calibration, rescoring, normalization drift, saturation detection, or any code in src/utils/scoring/, src/utils/metrics.py, or src/utils/calibration.py. Also use when debugging score values, investigating why a worker scored unexpectedly, or modifying the scoring contract.
| name | git-conventional-commits |
| description | ALWAYS use this skill when committing code changes. Creates commits following conventional commit format. Trigger on any commit, git commit, save changes, or commit message task. |
Follow these conventions when creating commits.
Before committing, always check the current branch:
git branch --show-current
If you're on main or master, you MUST create a feature branch first — unless the user explicitly asked to commit to main. Do not ask the user whether to create a branch; just proceed with branch creation.
<type>(<scope>): <subject>
<body>
<footer>
The header is required. Scope is optional. All lines must stay under 100 characters.
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
refactor | Refactoring (no behavior change) |
perf | Performance improvement |
docs | Documentation only |
test | Test additions or corrections |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
style | Code formatting (no logic change) |
Scopes should reflect the project's modules or feature areas. Examples:
(api) - API endpoints or external interfaces(auth) - Authentication and authorization(core) - Core business logic(ui) - User interface components(db) - Database layer(scripts) - Utility scripts\n sequencesWhen creating commits from the CLI, do not embed escaped newlines like \n inside -m strings. That produces literal backslash characters in the final commit message.
Prefer one of these patterns:
git commit -m "type(scope): Subject" \
-m "First paragraph with real line wrapping.
Second paragraph.
Co-Authored-By: (the agent's name and attribution byline)"
git commit
Use the editor flow when the message needs careful formatting.
When changes were primarily generated by a coding agent, include the Co-Authored-By attribution in the commit footer. Agents should use their own identity:
Co-Authored-By: (the agent's name and attribution byline)
Example: Co-Authored-By: Claude Sonnet 4 <noreply@example.com>
This is the only indicator of AI involvement that should appear in commits. Do not add phrases like "Generated by AI", "Written with Claude", or similar markers in the subject, body, or anywhere else in the commit message.
fix(api): Handle null response in user endpoint
The user API could return null for deleted accounts, causing a crash
in the dashboard. Add null check before accessing user properties.
Co-Authored-By: (the agent's name and attribution byline)
feat(auth): Add role-based access control for admin endpoints
Restrict admin-only API routes to users with the 'admin' role.
Previously any authenticated user could access these endpoints.
refactor(viz): Extract common plot styling logic
Move matplotlib styling logic into a shared helper function. No behavior change.
Co-Authored-By: (the agent's name and attribution byline)