Systematic JUnit 5 patterns for testing numeric limits, null/empty cases, and edge conditions.
Run in your terminal
Covers numeric boundaries (Integer.MIN_VALUE, MAX_VALUE, zero), string edge cases (null, empty, whitespace), and collection sizes (empty, single, many)
Includes parameterized test examples using @ParameterizedTest and @ValueSource for efficient multi-case coverage
Demonstrates floating-point precision testing with tolerance-based assertions, overflow/underflow detection, and special values
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionunit-test-boundary-conditionsExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill unit-test-boundary-conditionsFetches unit-test-boundary-conditions from giuseppe-trisciuoglio/developer-kit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate unit-test-boundary-conditions. Access via /unit-test-boundary-conditionsin your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Package manager
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill unit-test-boundary-conditionsWorks with
0
total installs
0
this week
194
GitHub stars
0
upvotes
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
unit-test-boundary-conditions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend unit-test-boundary-conditions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
unit-test-boundary-conditions is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend unit-test-boundary-conditions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in unit-test-boundary-conditions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
unit-test-boundary-conditions reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 57