- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add retentioneering/retentioneering-tools --skill retentioneering-contributing -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/retentioneering/retentioneering-tools/tree/HEAD/.claude/skills/retentioneering-contributingपब्लिशर से
Convert a user's observation — a bug, a paper cut, a missing capability, a workaround they keep re-writing — into the smallest upstream change that would have prevented it, packaged so maintainers can accept it quickly.
Record four things while they are fresh:
retentioneering.__version__, Python, OS, install source
(pip wheel vs source checkout).Field lesson: reports formatted as expectation/reality/cost/repro get acted on; "X is broken" reports stall.
Many pain points are already fixed on v5-migration — verify before drafting:
git log --oneline -30 and CHANGELOG.md — search keywords from the observation.gh issue list --search "<keywords>", gh pr list ....Build the smallest toy that shows the gap, e.g.:
import pandas as pd
from retentioneering import Eventstream
df = pd.DataFrame({"user_id": ["u1","u1","u2"], "event": ["a","b","a"],
"timestamp": pd.date_range("2026-01-01", periods=3, freq="1min")})
# EXPECTED: ... ACTUAL: ...
Rules: synthetic data only (never the user's real log); deterministic (fixed frames, no randomness without seed); one behavior per repro; assert the expectation so the repro doubles as a failing test.
For API proposals, the accepted framing (from templates): problem → evidence of frequency → proposed signature → semantics incl. edge cases → acceptance criteria → migration notes.
Read references/repo-conventions.md first. Non-negotiables:
master-tracking v5-migration; one logical change per PR.make install-dev — installs deps (uv sync + npm install) and wires the git hook
(a one-time-per-clone step) so commits are auto-checked; skip it and commits bypass the hooks
locally and CI's lint job flags the formatting on your PR. Add make build only when
touching widgets/JS.path_col/event_col/timestamp_col/session_col,
start_anchor/end_anchor, verb-first processors, noun widgets, <widget>_data twins.duckdb.sql with replacement-scan idioms (superseded ADR-0002).tests/...); a bug fix MUST include the
failing-before test from Stage 3.uv run python docs/scripts/render_pages.py).uv run pre-commit run --all-files # ruff lint+format, gitleaks, hygiene
uv run pytest tests/ -v # full suite (CI runs 3.11–3.13)
uv run python docs/scripts/render_pages.py # if docstrings changed
Commit style: imperative, scoped, explaining WHY when non-obvious (see git log for the
house voice). Update CHANGELOG.md under the unreleased/current section for
user-visible changes.
Submit:
git push -u origin <branch>
gh pr create --title "<imperative summary>" --body-file pr_body.md
PR body (template in references/proposal-templates.md): what & why → linked issue →
repro/before-after → tests added → sync checklist (docs/MCP/JS if applicable) →
breaking-change note. CI must pass: lint + test (3.11/3.12/3.13). master is
PR-only; merging does not release (releases are tag-driven by maintainers).
Respond to review within the PR (avoid force-push after review starts; append commits). If maintainers ask for direction changes, update the issue first, then the code — the issue is the contract.
When the user accumulated a batch (e.g., a journal of friction from a project): deduplicate → verify each against current version (Stage 2) → rank by (frequency × silent-failure risk) → file the top 3–5 as separate issues with repros → offer one PR for the cheapest verified fix to build credibility, referencing the issues for the rest. Do not open one mega-issue.
>
---name: retentioneering-contributingdescription: >---# .claude/skills/retentioneering-contributing/SKILL.mdFAQ
पब्लिशर से .claude/skills/retentioneering-contributing/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/retentioneering/retentioneering-tools पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।