メニュー
Package DAL repository changes into commits and pull requests. Use when the user says to commit, push, open a PR, update a PR, ship it, send for review, or wrap up current work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write Google Test unit tests and fix failing test sets for the DAL C++ quantitative finance library. Use when the user asks to write tests, add test coverage, create unit tests, repair broken tests, fix failing test suites, or mentions testing for new or existing C++ code. Also trigger when implementing features that need test coverage, refactoring code without tests, or when the user mentions a function/class that should be tested.
Run and inspect this repository's build and Google Test workflow. Use when the user asks to run all tests, verify the whole codebase, execute the Linux or Windows build/test scripts, inspect `test_output.txt`, or confirm whether the test suite passes.
Start or stop the DAL derivatives portfolio web UI (FastAPI backend + React/Vite frontend). Use when the user says "start the web UI", "run the Web UI", "stop the web UI", "shut down the Web UI", "launch the dashboard", or anything about bringing the DAL web UI up or down. On Windows/PowerShell 7 it uses the `.ps1` scripts; elsewhere it uses the `.sh` scripts.
Work on the DAL web UI and backend. Use when starting or stopping the FastAPI/React app, changing `dal-web/`, running backend/frontend/e2e tests, applying the industrial terminal UI style, or enforcing async backend rules.
Commit current repository changes, push to a remote branch, and create or update a pull request. Use when the user says "ship it", "commit and PR", "push and create PR", "send this up for review", "wrap this up", or any variation of committing, pushing, and opening or updating a PR in one workflow.
Review changed C++ code and DAL markdown guidance for compliance with this project's coding, unit test, and documentation style. Use when the user asks to review code style, check style compliance, lint code, verify naming conventions, review changed files for project conventions, check .claude markdown guidance, or says "review my changes", "check the style", "does this follow our conventions", or similar.
| name | dal-git-pr |
| description | Package DAL repository changes into commits and pull requests. Use when the user says to commit, push, open a PR, update a PR, ship it, send for review, or wrap up current work. |
Use this skill to turn completed work into focused commits and a PR. Preserve unrelated user changes and never stage dirty submodule contents or generated build artifacts.
Load both the shared DAL git conventions and the complete publish workflow before changing Git or GitHub state.
git status --short
git diff --stat
git diff --staged --stat
git log --oneline -5
master if currently on master.git diff --cached --name-status and validate it with
git diff --cached --check.gh pr merge --match-head-commit <sha> as detailed in the
publish workflow.Use one logical change per commit:
Add log-linear interpolation
Explain why the change is needed and what behavior it enables.
Do not append co-author trailers unless the user explicitly asks.
Use this shape:
## Summary
- <key change>
- <key change>
## Test plan
- [x] <targeted test or build>
- [x] <full suite or rationale if not run>
Allowed PR title prefixes: feat:, fix:, docs:, chore:, refactor:, test:,
style:, perf:, ci:. Use draft PRs for unfinished work.
Stage submodule pointer updates only when intentional. Do not stage dirty submodule working tree contents.