test
Skill0 starsChanged 3 months agoMITView on GitHub
Run unit tests or specific integration test categories. Use after making code changes to verify correctness.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- Renozoic-Foundry/forge-publictheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- RohiRIK/skillstheir own version, first seen Nov 15, 2026
- isksss/skillstheir own version, first seen Nov 15, 2026
- oberemokis/skillstheir own version, first seen Nov 15, 2026
- tyrantpiper/travel-pwatheir own version, first seen Nov 8, 2026
Used with
Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- parcadeiSkill
agentica-infrastructure
Reference guide for Agentica multi-agent infrastructure APIs
Also in 3 projects that use this
- +10 more from parcadei
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- react/react★ 252ksame name
- facebook/react★ 252ksame name
- apache/skywalking★ 25ksame name
- livewire/livewire★ 24ksame name
- NVIDIA/TensorRT★ 13ksame name
- FalkorDB/FalkorDB★ 10ksame name
- FastLED/FastLED★ 7.5ksame name
- fleetdm/fleet★ 7.2ksame name
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
175 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- cleanup-worktreeSkill
- db-querySkill
- db-searchSkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- devops-workitem-updateSkill
- finalize-taskSkill
- find-codeSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- prSkill
- rebase-mainSkill
- starttaskSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 158 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
Default to unit api if no arguments
- Distinctive: line 47
Run the appropriate test command
- Distinctive: line 53
Always specify a category for integration tests.
- Very specific: line 57
Use Assert.Fail(), never Assert.Ignore() or Assert.Inconclusive()
“Common” is measured: kept by at least 6 in 10 of the 158 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run Tests
Arguments: $ARGUMENTS
Test projects
| Project | Type | Path |
| API Unit Tests | Unit | Contoso.Payments.Api/Contoso.Payments.API.UnitTests/ |
| API Integration Tests | Integration | Contoso.Payments.Api/Contoso.Payments.API.IntegrationTests/ |
| Web Unit Tests | Unit | Contoso.Payments/Contoso.Payments.UnitTests/ |
| Web Integration Tests | Integration | Contoso.Payments/Contoso.Payments.IntegrationTests/ |
Commands
Unit tests (quick, safe to run all):
dotnet test {test-project-path} -p:WarningLevel=0Integration tests (run specific category only!):
dotnet test {test-project-path} --filter "FullyQualifiedName~{CategoryName}" -p:WarningLevel=0Integration test categories (API)
List your test fixture classes here, grouped by theme, so the model can pick a category by name instead of running everything. Example shape:
Core: CoreFunctionalityTests, SystemValidationTests
Business Rules: DuplicateTransactionTests, VelocityLimitTests, GeographicRestrictionTests
Routing: ProcessorSelectionTests, ProcessorCoverageTests
Card/Security: CardTypeDetectionTests, PrepaidCardTests, BinRulesTests
Errors: ErrorCodeValidationTests
Your task
- Parse arguments to determine test type and scope
- Default to
unit apiif no arguments - Run the appropriate test command
- Set timeout to 600000ms for integration tests
CRITICAL WARNING
NEVER run all integration tests - this takes over 1 hour! Always specify a category for integration tests.
Testing guidelines
- Use
Assert.Fail(), neverAssert.Ignore()orAssert.Inconclusive() - Integration tests may take 5-10 minutes per category
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.