point-in-time-guardrails

Estrelas0

Forks0

Atualizado4 de maio de 2026 às 19:34

Use whenever modifying SnapshotBuilder, provider fetch methods, bundle export/load logic, date filters, or any code that could leak future information into snapshots or backtests. Trigger on look-ahead bias concerns, as_of propagation, report_date handling, benchmark joins, sector map timing, or changes to snapshot schemas and validation.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

YoungseokOh

YoungseokOh/eit-market-data

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	point-in-time-guardrails
description	Use whenever modifying SnapshotBuilder, provider fetch methods, bundle export/load logic, date filters, or any code that could leak future information into snapshots or backtests. Trigger on look-ahead bias concerns, as_of propagation, report_date handling, benchmark joins, sector map timing, or changes to snapshot schemas and validation.

Point-in-Time Guardrails

Use this skill whenever data timing semantics might change.

Core Rule

Every value in a snapshot must be knowable on or before decision_date.

Workflow

Trace as_of from CLI or builder entrypoint to each provider call.
Reject any path that uses date.today() or a fixed future end date for runtime data.
Check filing and fundamentals by actual publication date, not fiscal period alone.
Add or update tests that assert no future-dated bars or quarters enter the snapshot.
If the change touches bundle fields consumed by eit-research, verify that contract too.

Commit Format

If you make a commit while using this skill, follow @rules/commit-messages.md: <type>: <message> then a blank line then <body>.

Mais deste repositório

mesmo repositório

kr-bundle-pipeline

YoungseokOh/eit-market-data

Use when building, validating, or debugging KR snapshot bundles and the daily batch flow. Trigger on build_kr_snapshot.py, run_daily_batch.py, snapshot.json, manifest.json, summary.json, GitHub Actions daily-market-data.yml, ci_safe profile behavior, or eit-research bundle loading.

2026-05-040

krx-auth-recovery

YoungseokOh/eit-market-data

Use when official KRX-backed pykrx paths fail in eit-market-data. Trigger on KRX login changes, `KrxAuthRequired`, `LOGOUT`, `400`, `KeyError('지수명')`, empty KRX index or listing frames, pykrx dataframe column errors like missing `종가`/`BPS`/`PER`, browser cookie/profile issues, or when scripts/krx_login.py and src/eit_market_data/kr/krx_auth.py need to be modified or debugged.

2026-05-040

market-data-preflight

YoungseokOh/eit-market-data

Use before running Korean market-data collection, bundle export, or daily batch commands in eit-market-data. Trigger when the user wants to run or debug preflight, crawl_kr_data_pykrx.py (official raw collection), `crawl_kr_data_fallback.py` (legacy FnGuide repair path), `crawl_kr_data.py` (legacy authenticated recovery), build_kr_snapshot.py, run_daily_batch.py, GitHub Actions data jobs, or local environment setup. Also use when validating API keys, package installation, output directories, or batch readiness.

2026-05-040

provider-maintenance

YoungseokOh/eit-market-data

Use when adding or changing market-data providers, provider factories, optional dependencies, scripts that call providers, or tests around DART, ECOS, FDR, pykrx, and snapshot assembly. Trigger on changes under src/eit_market_data/, pyproject optional dependencies, provider protocols, or new market-data fields and adapters.

2026-05-040

name	point-in-time-guardrails
description	Use whenever modifying SnapshotBuilder, provider fetch methods, bundle export/load logic, date filters, or any code that could leak future information into snapshots or backtests. Trigger on look-ahead bias concerns, as_of propagation, report_date handling, benchmark joins, sector map timing, or changes to snapshot schemas and validation.

Point-in-Time Guardrails

Use this skill whenever data timing semantics might change.

Core Rule

Every value in a snapshot must be knowable on or before decision_date.

Workflow

Trace as_of from CLI or builder entrypoint to each provider call.
Reject any path that uses date.today() or a fixed future end date for runtime data.
Check filing and fundamentals by actual publication date, not fiscal period alone.
Add or update tests that assert no future-dated bars or quarters enter the snapshot.
If the change touches bundle fields consumed by eit-research, verify that contract too.

Commit Format

If you make a commit while using this skill, follow @rules/commit-messages.md: <type>: <message> then a blank line then <body>.

point-in-time-guardrails

Point-in-Time Guardrails

Core Rule

Workflow

Read Next

Commit Format

Point-in-Time Guardrails

Core Rule

Workflow

Read Next

Commit Format