菜单
Use when creating branches, writing commits, or following repository Git conventions in this workspace. Follow the local branch naming and commit message patterns, including issue references when available.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Orquestar cuentas MetaTrader 5 del workspace actual usando MQL5\Scripts\interface.py, archivos accounts/account_id/info.md, accounts/account_id/bots.ini y notificaciones Telegram. Use when Codex is asked to orchestrate accounts, coordinate account-specific bots, prepare or inspect bots.ini for an MT5 account, or notify the configured Telegram chat/channel about account orchestration status.
Use the local MetaTrader 5 Python trading CLI at MQL5\Scripts\interface.py. Use when Codex needs to explain, run, validate, or troubleshoot command-line trading operations such as opening market or pending orders, setting or editing SL/TP, closing positions, canceling pending orders, listing opened trades or pending orders, reading recent trade history, or checking account and symbol details.
Analyze market regime and session structure in this MQL5 workspace using reusable CSV exports from an MQL5 script. Use when Codex needs to classify a market as Tendencial or Lateral with moving average and ATR, export per-session data to Terminal Common Files for M15, H1, and D1, and then read those CSV files directly to summarize insights and recommendations by session without recreating scripts that already exist.
Use when compiling MQL5 experts, indicators, scripts, or include-dependent code in this workspace from the terminal. Follow the local MetaEditor command pattern and always inspect the compilation log after running it.
Run MetaTrader 5 parameter optimizations in this workspace and summarize real results from exported optimization reports. Use when Codex needs to optimize EA inputs such as SL, TP, RSI values, or other inputs for experts under MQL5\Experts, by generating a tester .ini with [TesterInputs], launching MT5 from the terminal, and reading the resulting XML ranking.
Use when running MetaTrader 5 Strategy Tester backtests from the terminal in this workspace. Ask the user for the test configuration field by field before launching the test, using the current project defaults unless the user changes them.
| name | git |
| description | Use when creating branches, writing commits, or following repository Git conventions in this workspace. Follow the local branch naming and commit message patterns, including issue references when available. |
Use this skill when the user asks for help with branches, commits, or Git naming conventions in this repository.
Create short, lowercase branch names with hyphens. Use one of these prefixes:
feature/branch-namebug/branch-namehotfix/branch-namechore/branch-namedocs/branch-namerefactor/branch-nametest/branch-nameChoose the prefix by intent:
feature/ for new functionalitybug/ for defect fixes that are not urgent production fixeshotfix/ for urgent fixeschore/ for maintenance, config, tooling, or cleanupdocs/ for documentation-only changesrefactor/ for structural code improvements without intended behavior changetest/ for test-only additions or fixesExamples:
feature/add-git-skill
bug/fix-backtest-report-path
hotfix/repair-mt5-launch-command
chore/normalize-skill-path-placeholders
docs/update-run-backtests-skill
refactor/simplify-fvg-loader
test/add-backtest-config-coverage
Use this format for commit subjects:
type(scope): summary
Preferred example:
feat(skills): add git conventions skill
When there is a related issue, add a blank line and reference it like this:
feat(skills): add git conventions skill
refs #123
Use these commit types:
feat for new behavior or new functionalityfix for bug fixeshotfix for urgent production fixes when the repository uses a distinct hotfix commit typechore for maintenance or tooling updatesdocs for documentation changesrefactor for internal code restructuring without intended behavior changetest for test changesperf for performance improvementsbuild for build pipeline or dependency packaging changesci for CI workflow changesUse a short scope that matches the affected area.
Examples:
skillsbacktestscompilemt5docsKeep the summary short and action-oriented.
Good:
fix(backtests): use placeholder report path in ini example
Avoid:
fix(stuff): various updates
Use issue references when the repository tracks work with issue IDs.
refs #issue-id when the commit relates to an issuecloses #issue-id when the commit is intended to close the issueExamples:
fix(mt5): handle missing tester log gracefully
refs #45
docs(skills): clarify branch naming rules
closes #52
When preparing multiple commits for one branch:
If the work is small and tightly related, prefer one clean commit over many noisy commits.