Conversation
51300d2 to
6c4d24d
Compare
|
|
||
| ```bash | ||
| # Example with npm + turbo | ||
| npm run fix -- --filter=<workspace1> --filter=<workspace2> |
There was a problem hiding this comment.
same comment here about language agnostic
There was a problem hiding this comment.
Done in 3ef29f1. follow-up-on-pr now points at the create-pr CI-checks template (which is language-agnostic) and shows filter/target patterns across JS/TS monorepos, Python, Rust, Go, JVM, and Bazel.
| - You need both to answer: "what did the model receive?" and "what did it actually do?" | ||
|
|
||
| 3. **Use Bun's proxy env var explicitly** | ||
| - `BUN_CONFIG_PROXY` is the important one. |
There was a problem hiding this comment.
language/framework agnostic?
There was a problem hiding this comment.
Done in 3ef29f1. Rewrote http-toolkit-intercept as runtime-agnostic: the skill now works for any runtime that respects a proxy (Node.js, Bun, Deno, Python, Go, Ruby, JVM, .NET, PHP, Rust, curl/shell, Docker). Added a Runtime proxy matrix covering the proxy env vars / JVM flags and TLS-bypass options per runtime, and generalized the quick-start away from Bun specifics (Bun is still called out as a special case since it requires BUN_CONFIG_PROXY, but it's no longer the lead example). Also updated the plugin README and top-level README descriptions.
…framework agnostic Addresses PR #24 review feedback from @factory-davidgu. Generalize the three skills away from JS/TS (npm/turbo) and Bun/Node specifics: - create-pr: describe verification categories and show examples across ecosystems (JS/TS, Python, Rust, Go, JVM, Ruby) instead of hard-coded npm/turbo commands. - follow-up-on-pr: same generalization for the CI-check step. - http-toolkit-intercept: replace Bun-centric guidance with a runtime proxy matrix covering Node, Bun, Deno, Python, Go, Ruby, JVM, .NET, PHP, Rust, curl/shell, and Docker. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
No description provided.