jzills
UserA modular marketplace of custom Claude Code skills, plugins, hooks, and AI workflow extensions built for reusable agentic developer workflows.
Categories
Indexed Skills (12)
scaffold-integration-project
Use this skill when the user wants to create a new .NET integration test project from scratch. Trigger on: "create integration test project", "scaffold integration tests", "set up integration test project", "add integration tests to my solution", "create a test project for integration tests", "I don't have an integration test project yet", "bootstrap integration test infrastructure".
setup-test-infrastructure
Use this skill when the user wants to configure containers or Docker infrastructure for .NET integration tests. Trigger on: "set up containers for my tests", "configure docker for integration tests", "add testcontainers", "generate docker-compose for my tests", "set up test infrastructure", "what containers do I need", "configure test dependencies". Also invoked as a sub-skill when scaffolding a new integration test project.
write-integration-tests
Use this skill whenever the user asks to write, generate, or add integration tests for C# or .NET code. Trigger on: "write integration tests", "add integration tests", "test this endpoint", "test this API", "integration test for this controller", "test against the database", "write end-to-end tests", "test this repository with a real database", "add integration test coverage". Also trigger when the user shows a controller, repository, or service and asks for tests that require real infrastructure (database, message broker, HTTP, etc.) rather than mocks.
skill-changelog
Use this skill whenever a skill is being created, modified, or improved — including when writing or editing a SKILL.md, adding/removing references, updating scripts, or changing a skill description. Also trigger when a user says "add a changelog", "track skill changes", "initialize changelog", "update the changelog for this skill", "switch to auto", or "switch to opt-in". This skill must run as part of any skill editing workflow to ensure CHANGELOG.md stays current.
prompt-reviewer
Review and refine prompts to improve clarity, specificity, token efficiency, and missing context. Use this skill whenever the user hands you a prompt as an artifact and asks for feedback — regardless of the target model (Claude, ChatGPT, Midjourney, system prompts, etc.). Trigger when the user says "review this prompt", "improve my prompt", "refine this prompt", "make this prompt better", "is this prompt clear", "check this system prompt", "optimize this prompt", "fix my prompt", "critique this prompt", or any similar phrasing where a prompt is the subject of review rather than the instruction itself. Supports three modes: default (single-pass), --deep (guided dialogue), --variants (three rewrites). Also trigger when the user uses "--deep" or "--variants" flags alongside a prompt.
auto-rewind
Use when context contains `[AUTO-REWIND] Tests failed:`, when the user expresses rejection ("wrong", "broken", "undo", "not what I wanted"), or when Claude realizes prior edits were based on a wrong assumption. Do not fix forward — follow the rewind protocol instead.
dotnet-unit-tests
Use this skill whenever the user asks you to write, generate, add, or scaffold unit tests for C# or .NET code. Trigger on: "write tests for this", "add unit tests", "test this class", "generate tests", "cover this with tests", "write NUnit tests", "mock this dependency", "how do I test this", "add test coverage", "write a test for this method", or any request that involves C#/.NET testing. Also trigger proactively when the user shows you a C# class or method and asks you to improve, review, or complete it — if there are no tests, offer to write them.
github-pr
Creates GitHub pull requests for the authenticated user using the gh CLI. Use this skill whenever the user wants to open a PR, submit their work for review, push a branch and create a pull request, or says anything like "make a PR", "open a pull request", "create a PR", "submit for review", "push this up and PR it", or "ready to merge". Also trigger when the user has finished a feature or fix and mentions reviewing, merging, or sharing their changes — even if they don't say "pull request" explicitly. This skill handles branch detection, base branch selection, and title/description generation from git history. Creates regular PRs by default; only creates draft PRs when the user explicitly requests it.
python-pep8
Enforce PEP 8 style in Python code. Use this skill whenever the user shows you Python code and asks you to review, lint, format, clean up, or fix style issues — even if they don't say "PEP 8" explicitly. Also trigger when the user asks "is this good Python?", "check my code style", "format this", "clean this up", or "what's wrong with this Python?". Trigger proactively when writing new Python code to ensure it is PEP 8 compliant from the start. Also use when the user asks "what does PEP 8 say about X?", "how should I name this?", or any question about Python style conventions.
dotnet-xml-docs
Use when writing, reviewing, or generating XML documentation comments (///) for C# or .NET code. Trigger on: "add XML docs", "document this class", "write doc comments", "add IntelliSense comments", "document the API", "add triple-slash comments", "add summary comments", or any request involving /// documentation in C#/.NET. Also trigger proactively when the user asks to review or complete a public API surface that lacks documentation.
gitflow
Use when the repository has been identified as using GitFlow — a remote `develop` branch exists. Provides base branches, PR targets, and merge conventions for feature, release, and hotfix branches.
trunk
Use when the repository has been identified as trunk-based — no remote `develop` branch exists. Provides base branches and PR targets for all branch types.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.