Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

add-feature

Étoiles2

Forks0

Mis à jour1 juillet 2026 à 14:47

Procedure for adding a feature to gbcms following its Git Flow and Rust/Python architecture (branch from develop, plan the layer, implement, sync type stubs, add tests with the 4 counting invariants, update docs/CHANGELOG, QA, PR to develop). Use when starting new feature work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

msk-access

msk-access/gbcms

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	add-feature
description	Procedure for adding a feature to gbcms following its Git Flow and Rust/Python architecture (branch from develop, plan the layer, implement, sync type stubs, add tests with the 4 counting invariants, update docs/CHANGELOG, QA, PR to develop). Use when starting new feature work.

add-feature

Create feature branch:

git checkout develop && git pull origin develop
git checkout -b feature/<scope>-<description>

Plan the feature:
- Identify the layer: Rust counting, Python orchestration, CLI, or docs
- Check .agents/rules/architecture.md for the Rust/Python boundary
- Check existing code for reusable patterns (don't re-implement)
Implement:
- Rust: rust/src/ → rebuild with maturin develop --release
- Python: src/gbcms/
- CLI option: add to cli.py, validate in models/core.py
- Type stubs: update src/gbcms/_rs.pyi (the single stub for gbcms._rs)
- If it changes a CLI default/filter: update nextflow/nextflow.config too
Add tests: assert all 4 counting invariants; cover edge cases.
Update docs: docs/cli/*, docs/nextflow/parameters.md (if NF param), docs/reference/output-formats.md (if schema changed), CHANGELOG ## [Unreleased].
Run QA (see the qa-check skill).

PR to develop:

git push origin feature/<scope>-<description>
gh pr create --base develop --title "feat(<scope>): <description>"

Plus depuis ce dépôt

même dépôt

mfsd-analysis

msk-access/gbcms

Reference for gbcms mFSD (fragment size distribution) — the opt-in --mfsd flag, MAF/VCF column gating, KS test + LLR statistics, and Rust-native ZSTD Parquet output. Use when touching mfsd.rs, parquet_writer.rs, the mFSD report, or column-count tests.

2026-07-012

rust-python-ffi

msk-access/gbcms

Reference for the gbcms Rust/Python (PyO3) boundary — maturin build commands,

2026-07-012

rna-annotation

msk-access/gbcms

Reference for gbcms RNA mode — GTF-based transcript annotation (--gtf), the COITree AnnotationIndex, exon-boundary distance, per-transcript counts, and ASJD (allele-specific junction detection). Use when touching annotation/, rna.rs, or RNA output columns. Strandedness/sense-antisense gotchas live here.

2026-06-302

counting-engine

msk-access/gbcms

Reference for the gbcms counting core — genomic binning (10kb bins, one fetch per bin), the 4-phase variant-check pipeline, and alignment-backend dispatch. Use when modifying engine.rs or variant_checks.rs, debugging count discrepancies, or reasoning about binning and binned↔legacy parity. For fragment/consensus see fragment-counting; for filters/quality see read-filters-qc.

2026-06-262

debug-error

msk-access/gbcms

Procedure for diagnosing gbcms build/test/CI errors — Rust compile failures, PyO3 stub mismatches, COITree SIMD (nosimd vs NEON/AVX) issues, CI black/ruff version traps, and test failures. Use when hitting an error and you need the gbcms-specific triage path.

2026-06-262

fragment-counting

msk-access/gbcms

Reference for fragment-level counting in gbcms — R1/R2 quality-weighted consensus, FAD/FAF (fragment alt depth/fraction), QNAME/UMI deduplication, duplex vs singleton UMI families, strand consistency, and amplicon split. Use when touching shared/fragment.rs or any DPF/RDF/ADF logic, or debugging fragment-level VAF.

2026-06-262

name	add-feature
description	Procedure for adding a feature to gbcms following its Git Flow and Rust/Python architecture (branch from develop, plan the layer, implement, sync type stubs, add tests with the 4 counting invariants, update docs/CHANGELOG, QA, PR to develop). Use when starting new feature work.

add-feature

Create feature branch:

git checkout develop && git pull origin develop
git checkout -b feature/<scope>-<description>

Plan the feature:
- Identify the layer: Rust counting, Python orchestration, CLI, or docs
- Check .agents/rules/architecture.md for the Rust/Python boundary
- Check existing code for reusable patterns (don't re-implement)
Implement:
- Rust: rust/src/ → rebuild with maturin develop --release
- Python: src/gbcms/
- CLI option: add to cli.py, validate in models/core.py
- Type stubs: update src/gbcms/_rs.pyi (the single stub for gbcms._rs)
- If it changes a CLI default/filter: update nextflow/nextflow.config too
Add tests: assert all 4 counting invariants; cover edge cases.
Update docs: docs/cli/*, docs/nextflow/parameters.md (if NF param), docs/reference/output-formats.md (if schema changed), CHANGELOG ## [Unreleased].
Run QA (see the qa-check skill).

PR to develop:

git push origin feature/<scope>-<description>
gh pr create --base develop --title "feat(<scope>): <description>"