Add --isolate flag to all azpysdk calls in skill files

Co-authored-by: l0lawrence <100643745+l0lawrence@users.noreply.github.com>

Author: Copilot

.github/skills/fix-black/SKILL.md

@@ -23,12 +23,12 @@ Intelligently fixes black formatting issues by:
 
 **Command for entire package:**
 ```powershell
-python -m azpysdk black --pkg-path <package-path>
+python -m azpysdk --isolate black --pkg-path <package-path>
 ```
 
 **Command for specific file/module:**
 ```powershell
-python -m azpysdk black --pkg-path <package-path> -- path/to/file.py
+python -m azpysdk --isolate black --pkg-path <package-path> -- path/to/file.py
 ```
 
 ## Reference Documentation
@@ -92,13 +92,13 @@ Black is an auto-formatter — it rewrites files to comply with the style. Simpl
 **Format entire package:**
 ```powershell
 # Run black on the entire package (within activated venv)
-python -m azpysdk black --pkg-path <package-path>
+python -m azpysdk --isolate black --pkg-path <package-path>
 ```
 
 **Format specific files (if issue mentions specific files):**
 ```powershell
 # Run black on specific files (within activated venv)
-python -m azpysdk black --pkg-path <package-path> -- path/to/specific_file.py
+python -m azpysdk --isolate black --pkg-path <package-path> -- path/to/specific_file.py
 ```
 
 ### Step 4: Review Changes
@@ -119,7 +119,7 @@ Re-run black in check mode to confirm all files are now properly formatted:
 
 ```powershell
 # Verify formatting (within activated venv)
-python -m azpysdk black --pkg-path <package-path>
+python -m azpysdk --isolate black --pkg-path <package-path>
 ```
 
 If black reports no files were changed, all formatting issues are resolved.
@@ -194,7 +194,7 @@ The Azure SDK for Python uses a repo-wide black configuration located at `eng/bl
 - Line length: 120 characters
 - Target Python versions: 3.8+
 
-The `python -m azpysdk black` command automatically uses this configuration, so no manual configuration is needed.
+The `python -m azpysdk --isolate black` command automatically uses this configuration, so no manual configuration is needed.
 
 ## Common Black Formatting Changes
 
@@ -225,14 +225,14 @@ pip install -r dev_requirements.txt
 pip install -e .
 
 # 2. Run black to auto-format the package
-python -m azpysdk black --pkg-path sdk/storage/azure-storage-blob
+python -m azpysdk --isolate black --pkg-path sdk/storage/azure-storage-blob
 
 # 3. Review what changed
 git diff --name-only
 git diff
 
 # 4. Verify no remaining issues
-python -m azpysdk black --pkg-path sdk/storage/azure-storage-blob
+python -m azpysdk --isolate black --pkg-path sdk/storage/azure-storage-blob
 
 # 5. Create PR referencing the issue
 $branchName = "style/azure-storage-blob-black-99999"

.github/skills/fix-mypy/SKILL.md

@@ -26,12 +26,12 @@ Intelligently fixes mypy issues by:
 
 **Command for entire package:**
 ```powershell
-python -m azpysdk mypy --pkg-path <package-path>
+python -m azpysdk --isolate mypy --pkg-path <package-path>
 ```
 
 **Command for specific file/module:**
 ```powershell
-python -m azpysdk mypy --pkg-path <package-path> -- path/to/file.py
+python -m azpysdk --isolate mypy --pkg-path <package-path> -- path/to/file.py
 ```
 
 ## Reference Documentation
@@ -98,13 +98,13 @@ Based on the GitHub issue details, determine which files to check:
 **Option A - Issue specifies files:**
 ```powershell
 # Run mypy on specific files mentioned in the issue (within activated venv)
-python -m azpysdk mypy --pkg-path <package-path> -- path/to/specific_file.py
+python -m azpysdk --isolate mypy --pkg-path <package-path> -- path/to/specific_file.py
 ```
 
 **Option B - Issue mentions module/directory:**
 ```powershell
 # Run mypy on entire package (within activated venv)
-python -m azpysdk mypy --pkg-path <package-path> -- azure/specific/module/
+python -m azpysdk --isolate mypy --pkg-path <package-path> -- azure/specific/module/
 ```
 
 **Option C - Check modified files (if no specific target):**
@@ -119,7 +119,7 @@ git diff --cached --name-only | Select-String "<package-path>"
 
 ```powershell
 # Run mypy targeting the specific area from the issue (within activated venv)
-python -m azpysdk mypy --pkg-path <package-path> -- <target-from-issue>
+python -m azpysdk --isolate mypy --pkg-path <package-path> -- <target-from-issue>
 ```
 
 ### Step 5: Analyze Type Errors
@@ -342,7 +342,7 @@ pip install -e .
 $targetFile = "azure/storage/blob/_blob_client.py"
 
 # 3. Run mypy on specific file
-python -m azpysdk mypy --pkg-path sdk/storage/azure-storage-blob -- $targetFile
+python -m azpysdk --isolate mypy --pkg-path sdk/storage/azure-storage-blob -- $targetFile
 
 # 4. Analyze output and identify fixable issues
 # Cross-reference with GitHub issue #67890
@@ -353,7 +353,7 @@ grep -r "from typing import" azure/storage/blob/ | findstr "_blob_client"
 # 6. Apply fixes to identified files
 
 # 7. Re-run mypy to verify
-python -m azpysdk mypy --pkg-path sdk/storage/azure-storage-blob -- $targetFile
+python -m azpysdk --isolate mypy --pkg-path sdk/storage/azure-storage-blob -- $targetFile
 
 # 8. Report results
 

.github/skills/fix-pylint/SKILL.md

@@ -26,12 +26,12 @@ Intelligently fixes pylint issues by:
 
 **Command for entire package:**
 ```powershell
-python -m azpysdk pylint --pkg-path <package-path>
+python -m azpysdk --isolate pylint --pkg-path <package-path>
 ```
 
 **Command for specific file/module:**
 ```powershell
-python -m azpysdk pylint --pkg-path <package-path> -- path/to/file.py
+python -m azpysdk --isolate pylint --pkg-path <package-path> -- path/to/file.py
 ```
 
 ## Reference Documentation
@@ -96,13 +96,13 @@ Based on the GitHub issue details, determine which files to check:
 **Option A - Issue specifies files:**
 ```powershell
 # Run pylint on specific files mentioned in the issue (within activated venv)
-python -m azpysdk pylint --pkg-path <package-path> -- path/to/specific_file.py
+python -m azpysdk --isolate pylint --pkg-path <package-path> -- path/to/specific_file.py
 ```
 
 **Option B - Issue mentions module/directory:**
 ```powershell
 # Run pylint on entire package (within activated venv)
-python -m azpysdk pylint --pkg-path <package-path> -- azure/specific/module/
+python -m azpysdk --isolate pylint --pkg-path <package-path> -- azure/specific/module/
 ```
 
 **Option C - Check modified files (if no specific target):**
@@ -117,7 +117,7 @@ git diff --cached --name-only | Select-String "<package-path>"
 
 ```powershell
 # Run pylint targeting the specific area from the issue (within activated venv)
-python -m azpysdk pylint --pkg-path <package-path> -- <target-from-issue>
+python -m azpysdk --isolate pylint --pkg-path <package-path> -- <target-from-issue>
 ```
 
 ### Step 5: Analyze Warnings
@@ -291,7 +291,7 @@ pip install -e .
 $targetFile = "azure/storage/blob/_blob_client.py"
 
 # 3. Run pylint on specific file
-python -m azpysdk pylint --pkg-path sdk/storage/azure-storage-blob -- $targetFile
+python -m azpysdk --isolate pylint --pkg-path sdk/storage/azure-storage-blob -- $targetFile
 
 # 4. Analyze output and identify fixable issues
 # Cross-reference with GitHub issue #12345
@@ -302,7 +302,7 @@ grep -r "similar_pattern" azure/storage/blob/
 # 6. Apply fixes to identified files
 
 # 7. Re-run pylint to verify
-python -m azpysdk pylint --pkg-path sdk/storage/azure-storage-blob -- $targetFile
+python -m azpysdk --isolate pylint --pkg-path sdk/storage/azure-storage-blob -- $targetFile
 
 # 8. Report results