📈 Add Rudder-specific usage telemetry - #93
Merged
Conversation
Co-authored-by: Codex Agent <codex@openai.com>
📦 No plugin release on mergeThe plugin package, tag, and GitHub Release already exist for |
|
Ready to review this PR? Stage has broken it down into 6 individual chapters for you: Chapters generated by Stage for commit 0897ce6 on Jul 30, 2026 4:43pm UTC. |
Co-authored-by: Codex Agent <codex@openai.com>
Co-authored-by: Codex Agent <codex@openai.com>
Co-authored-by: Codex Agent <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds privacy-preserving Rudder lifecycle telemetry for captured intent, context snapshots, test backups, generated-test scope, behavioral questions, and verified run outcomes without collecting raw prompts or generic model, token, tool, or cost data.
Repository, branch, and run identifiers are pseudonymized with a local secret; canonical
DO_NOT_TRACK=1remains a hard gate and telemetry remains best-effort.Rudder helpers and workflow instructions now carry run IDs, back up untracked tests, measure test-line snapshots, and report completion metrics.
The diff coverage threshold is now 90%, with
npm run typecheck, all 41 tests, andnpm run buildpassing.Greptile Summary
Adds privacy-preserving, pseudonymized Rudder lifecycle telemetry.
Confidence Score: 4/5
The base-ref handoff needs to be fixed before merging so completion telemetry cannot be lost or measured against a different scope from the run.
The initial helper may resolve an omitted base automatically, but the workflow retains only the run ID while later helpers require a base argument and recompute metrics from it.
Files Needing Attention: skills/rudder/SKILL.md, skills/rudder/scripts/telemetry.mjs
Important Files Changed
Sequence Diagram
sequenceDiagram participant Agent participant Context as context.mjs participant Backup as backup-tests.mjs participant Complete as telemetry.mjs participant Hook as rudder-prompt-hook Agent->>Context: start [--base target-ref] Context-->>Agent: rudderRunId, baseRef, mergeBase Agent->>Backup: runId + target-ref Backup->>Hook: test-backup-created Agent->>Complete: runId + target-ref + outcome Complete->>Hook: run-finished Note over Agent,Complete: Later calls must reuse Context's resolved baseRefReviews (1): Last reviewed commit: "📈 Add Rudder usage telemetry" | Re-trigger Greptile