TE
test-plugins-build-commands
>
Install
mkdir -p .claude/skills/test-plugins-build-commands && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14619" && unzip -o skill.zip -d .claude/skills/test-plugins-build-commands && rm skill.zipInstalls to .claude/skills/test-plugins-build-commands
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
This skill covers testing plugins for various repository types. Trigger: Load this skill when working with test_plugins.120 chars✓ has a “when” trigger
About this skill
<!-- L1:START -->
test-plugins-build-commands
This skill covers testing plugins for various repository types.
Trigger: Load this skill when working with test_plugins.
<!-- L1:END --> <!-- L2:START -->Quick Reference
| Task | Pattern |
|---|---|
| Map Python repositories | python_repo_map |
| Map Node repositories | node_repo_map |
Critical Patterns (Summary)
- Python Repository Mapping: Use
python_repo_mapto map Python repositories. - Node Repository Mapping: Use
node_repo_mapto map Node.js repositories.
Critical Patterns (Detailed)
Python Repository Mapping
Utilize python_repo_map to effectively map Python repositories for testing.
# Example of using python_repo_map
repo_mapping = python_repo_map()
Node Repository Mapping
Leverage node_repo_map to map Node.js repositories for your testing needs.
# Example of using node_repo_map
node_mapping = node_repo_map()
When to Use
- When you need to test Python plugins in a repository.
- When you are validating Node.js plugins in your project.
Commands
pytest tests/test_plugins.py
Anti-Patterns
Don't: Hardcode Repository Paths
Hardcoding paths can lead to maintenance issues and reduce flexibility.
# BAD
repo_path = "/path/to/repo"