Skip to content

fix(debugging-patterns): trace config to SDK consumers before refactors#20

Open
amit221 wants to merge 1 commit intoromiluz13:mainfrom
amit221:fix/issue-18
Open

fix(debugging-patterns): trace config to SDK consumers before refactors#20
amit221 wants to merge 1 commit intoromiluz13:mainfrom
amit221:fix/issue-18

Conversation

@amit221
Copy link
Copy Markdown

@amit221 amit221 commented Mar 20, 2026

Summary

  • Adds Phase 1 investigation step Trace configuration to its consumer (third-party SDKs, env, import time) in plugins/cc10x/skills/debugging-patterns/SKILL.md: prioritize an Option Zero config/env-only fix, trace who reads env when it is not passed through constructors (including import-time process.env usage), verify configuration via docs or installed sources before proposing SDK replacement, and treat comments about import-time behavior as investigation breadcrumbs.
  • Extends the anti-pattern list with proposing SDK replacement or large migration before ruling out a config-only fix and tracing env/config consumers at import time.

Addresses the workflow described in #18 (trace configuration to consumers before jumping to replacements).

How to test

From the repository root:

python3 plugins/cc10x/scripts/cc10x_harness_audit.py && python3 plugins/cc10x/scripts/cc10x_workflow_replay_check.py

Fixes #18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Suggestion: debugging-patterns — trace env vars to third-party SDK consumers before proposing replacements

2 participants