AGENT SKILL

trader-issue-workflow

Fix pcore-trader issues end-to-end — GitHub issues plus docs/issues/OBS-* files. Use when told to "fix open issues", triage observer-reported problems, or ship per-issue commits with tests. Covers triage order, per-issue commit discipline, duplicate-issue folding, and verification commands.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
trader-issue-workflow
description
Fix pcore-trader issues end-to-end — GitHub issues plus docs/issues/OBS-* files. Use when told to "fix open issues", triage observer-reported problems, or ship per-issue commits with tests. Covers triage order, per-issue commit discipline, duplicate-issue folding, and verification commands.

03 SKILL.md 正文

P-Core Trader Issue Workflow

Intake

gh issue list --repo P-Core-System/pcore-trader --state open --limit 60 \
  --json number,title --jq '.[] | "#\(.number) \(.title)"'

Also read docs/issues/OBS-YYYYMMDD-*.md (agent-filed issues with evidence tables) and docs/issues/INDEX.md. Docs files reference commits by hash — check whether the fix commit already exists in the merged tree before implementing:

git log --oneline | grep -i <hash-prefix>

Many "open" issues are already fixed on main but not deployed or not closed — verify first, then close with the commit reference instead of re-implementing.

Discipline

  • One commit per issue/task. Message: fix(scope): <what> (#NNN); body explains root cause.
  • Fold duplicates (e.g. two "zero limit orders" files with the same cause) into one fix and reference all IDs in the commit.
  • Each fix needs a regression test beside it when behavior (not docs) changes; run the focused suite before committing: python -m pytest tools/crypto/tests/test_<area>.py -q -p no:cacheprovider.
  • Merge remote before pushing (git pull --no-rebase): the server auto-commits deploys and agents push concurrently — expect non-fast-forward rejections.
  • After code fixes: deploy per the trader-ops skill (git pull on server + restart services), then close/label issues and update context/progress-tracker.md.

Triage order

  1. Crash-level: services in failed state, syntax errors in merged main (compile the whole hot path: venv/bin/python -m py_compile tools/crypto/*.py on the server before restarting).
  2. P0 data/trading (wrong signals, orders never placed, quota overruns).
  3. P1 ops (fail-open probes, unproven ids, alert quality).
  4. P2 enhancements (strategy upgrades, event-driven triggers) — each may be its own PR cycle.

Signal-gate debugging (recurring theme)

Zero signals = a gate chain rejects everything. Walk gates in order with signal_bot --scan output: MTF cascade (3/4 TFs) → conviction gate (CRYPTO_SIGNAL_MIN_CONFIDENCE, code default 0.35 but server .env may pin higher) → range/ADX/quorum gates. Bypass paths (1d-trend + 15m-entry) must run before hard skips; ordering bugs made them dead code (OBS-20261106-a1b2c3d4).

04 同仓库更多 Skills

P-Core-System
P-Core-System/pcore-orchestra

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

web-perf

Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

web-design-master

Professional web design standard ("AI Professional Web Design Master Prompt") covering page/section/layout design, visual hierarchy, color systems, typography scales, 8-point grid spacing, responsive breakpoints, accessibility, and design QA review. Use when designing or building any page, section, or layout so it looks deliberately designed by a professional product team rather than a generic AI template.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

verification-before-completion

Require command evidence before claiming done. Use proactively before VERIFY_PASS, ORCHESTRA_COMPLETE, or "all fixed" statements. Run tests, lint, health, or git checks — never trust claims without output.

★ 0
P-Core-System
P-Core-System/pcore-orchestra

ui-ux-pro-max

UI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML/CSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.

★ 0