원클릭으로
git-workflow
Git workflow conventions, conventional commits, and PR patterns for kreview
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Git workflow conventions, conventional commits, and PR patterns for kreview
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Testing conventions, patterns, and best practices for kreview. MANDATORY reading before adding or modifying tests.
nbdev cell directives, module export conventions, editing workflow, and testing patterns for notebook-first development. MANDATORY reading before editing any kreview Python module.
5-tier ctDNA labeling hierarchy with IMPACT tissue rescue, CH hotspot filtering, configurable VAF/variant thresholds, and continuous VAF regression stats.
How to parse cBioPortal MAF, SV, CNA, and clinical files for the labeling pipeline.
Structured debugging framework for kreview data pipeline issues
DuckDB glob scan patterns, connection management, and performance for kreview
| name | git-workflow |
| description | Git workflow conventions, conventional commits, and PR patterns for kreview |
| Prefix | When to Use | Example |
|---|---|---|
feat | New evaluator, metric, visualization | feat(fsc): add FSC.gene evaluator |
fix | Bug fix in existing code | fix(labels): handle missing IMPACT sample |
refactor | Code restructuring, no behavior change | refactor(eval): extract common plotting |
docs | mkdocs pages, docstrings, README | docs(labeling): add hierarchy flowchart |
test | New/fixed test cells | test(fsc): add edge case for empty parquet |
chore | Dependencies, CI, build config | chore: bump duckdb to 1.2.0 |
data | Label configs, thresholds | data(labels): add VAF 2% config |
main ← stable releases only
└── develop ← integration branch
├── feature/fsc-gene-evaluator
├── feature/wps-background-evaluator
├── fix/labels-missing-impact
└── docs/quickstart-guide
- [ ] `ruff check` passes
- [ ] `black --check` passes
- [ ] `nbdev-test` passes
- [ ] `mkdocs build --strict` passes
- [ ] No `.parquet` or data files committed
- [ ] Conventional commit messages
- [ ] Docstrings on all public functions