jenkinsci

Generates production-ready code for the Black Duck Security Scan Jenkins Plugin. Drives discovery of existing patterns, designs changes against codebase conventions, generates complete implementation with tests, and audits for breaking changes. Use when user says "implement", "implement feature", "implement this", "add support for", "add parameter", "add scan product", "write the code for", or any request to build new plugin functionality. Triggered via /plugin-code-generator.

Deep code explanations for Black Duck Security Scan Jenkins Plugin. When a user asks "how does X work", "explain the flow", "walk me through", or "what happens when", this skill provides structured walkthroughs covering entry points, call chains, layer-by-layer logic, and design intent. Triggered via /plugin-code-explainer or when user asks for architecture/flow understanding, data flow tracing, or reasoning behind implementation choices. Use this skill whenever the user wants to understand WHY the code is designed a certain way, not just WHAT it does.

Code quality review for Black Duck Security Scan Jenkins Plugin. Audit patterns, test coverage, exception handling, Jackson/LoggerWrapper usage, and architecture alignment. Use when user asks to review code, a PR, or a diff in this plugin repo — especially when changes touch service/, extension/, or global/ code. Triggered via /plugin-code-review. Do NOT use the generic code-review skill for this repo; use this one instead.

Security audit for Black Duck Security Scan Jenkins Plugin. Audit credential handling, CLI parameter injection, log masking, input validation, JSON safety, and SCM/artifact security. Use when user asks for security review, security audit, or to check for vulnerabilities in this plugin repo — especially when changes touch credential, parameter, or logging code. Triggered via /plugin-security-review. Do NOT use the generic security-review skill for this repo; use this one instead.

Run the Maven test cases for the P4 Jenkins plugin. Use when asked to run tests, run a specific test class or method, re-run failing tests, or verify tests pass. This skill only runs tests — it does not write or modify code.

Write a test for the P4 Jenkins plugin that covers every requirement / acceptance criterion, following the repo's JUnit 5 + JenkinsRule + p4d conventions. Use when asked to write or improve a test, add test coverage, or as the Red step of TDD before implementing a ticket.

Add a new language translation to a Java project using ResourceBundle-based i18n. Translates all entries, verifies quality via independent Google Translate back-translation, adds tests, updates docs, and handles git workflow. Use this skill whenever the user asks to add a translation, translate to a new language, add a locale, or do i18n work on a Java project with .properties files.

Review Jenkins plugin pull requests for common merge risks, including security, Jenkins extension patterns, compatibility, UI/CSP, dependencies, tests, documentation, and CI status. Use for general PR review without hardcoding project-specific files or feature rules.