nsheaps/test
plugins/sdlc-utils/skills/test/SKILL.md
Testing strategy and validation. Use when the user asks about "test strategy", "writing tests", "test coverage", "test plan", "validation", "QA", "how to test this", or when defining testing requirements for a feature. Covers test types, coverage expectations, and validation workflows.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl testInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 4:17 PM37.4s1 file scanned
SKILL.md
- name:
- test
- description:
- >
Testing
Guidelines for testing during the software development lifecycle.
Test Types
| Type | Scope | When to write | | ----------- | ---------------------------- | -------------------------- | | Unit | Individual functions/modules | During implementation | | Integration | Component interactions | After components are built | | E2E | Full user workflows | After integration | | Smoke | Critical path verification | Before deployment |
Workflow
Step 1: Define Test Strategy
Before writing tests, determine:
- What needs to be tested (from the spec)
- What test types are appropriate
- What the project's existing test patterns look like
- What tools/frameworks are already in use
Step 2: Write Tests
- Follow existing test patterns in the codebase
- Test behavior, not implementation details
- Cover happy paths, error paths, and edge cases
- Keep tests independent and deterministic
- Name tests descriptively (what is being tested and expected outcome)
Step 3: Validate Coverage
- Run the full test suite, not just new tests
- Check that new code has adequate coverage
- Verify tests actually catch the bugs they claim to prevent
- Ensure CI runs the same tests as local
Step 4: Maintain Tests
- Update tests when requirements change
- Delete tests for removed functionality
- Keep test execution fast (prefer unit over E2E where possible)
Coverage Expectations
- New code: aim for meaningful coverage of all public interfaces
- Bug fixes: must include a regression test
- Refactors: existing tests should still pass without modification
Anti-Patterns
| Anti-Pattern | Instead | | ----------------------- | ----------------------------------------- | | Testing implementation | Test behavior and outputs | | Flaky tests | Make tests deterministic | | Testing only happy path | Cover errors and edge cases | | Skipping CI validation | CI is the source of truth | | Giant test files | Organize tests to mirror source structure |
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/spec-management
tools
VerifiedTrustedCommunity
Manages spec files for requirements capture and validation
3SKILL.mdUpdated Jun 7, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026