Make your coding agents automatically self-improve. Enforce your coding standards while your developers keep using whatever IDE, model, or agent they want.
Add tests that cover core concepts and prevent regressions without overfitting or crystallizing the code base. Use when the user asks for tests, more coverage, or a regression test for a bug fix, or invokes /z:addtests.
Run a guided, end-to-end code assessment — frame the engagement, onboard the codebase's requirements via the setup skill, run zenable check plus an AI review pass against those same requirements, merge and verify the findings, and produce a polished HTML report bundle. Use this skill whenever the user asks to "scan", "audit", "review", or "assess" a codebase against custom requirements, compliance frameworks, or security concerns; whenever they want a deliverable report (PDF/HTML) summarizing a code review engagement; or whenever they invoke /z:assessment. Also trigger for phrases like "do a security review of this repo", "build me a compliance scan report", "I need to audit this codebase against X", or "scan this code for Y".
Expert debugging using the scientific method to identify root causes, forming and falsifying hypotheses against observable evidence. Use when the user reports a bug, a failing test, or unexplained behavior, or invokes /z:debug.
Double check work for quality, test coverage, elegance, hallucinations, and orphaned code left behind by changes on this branch. Use when the user asks you to review or verify your own work before shipping, or invokes /z:doublecheck.
Implement a new feature with research, a PRD, SOLID design, non-overfitted tests, and incremental commits. Use when the user asks to build, add, or implement a feature, or invokes /z:feat.
Reviews code changes against your Zenable requirements using hybrid LLM-as-judge analysis and Zenable's deterministic guardrails. Automatically invoked when making code changes or at development milestones. Use for security compliance, quality checks, and policy enforcement, or when the user invokes /z:guardrails-reviewer.
Address every unresolved pull request comment on the current branch's PR by making code changes or replying, then mark each thread as addressed. Use when the user asks to handle PR feedback or review comments from human reviewers, or invokes /z:prfeedback.
Expert help resolving Git merge conflicts with non-destructive merges that preserve behavior from both sides. Use when the user is merging or rebasing main into a feature branch, hits conflict markers, or invokes /z:rebase.
Research and summarize the intent, current state, rationale, and outstanding work for the current branch, including its pull request status. Use when the user asks what a branch is for, where it stands, or what is left to do, or invokes /z:researchbranch.
Guided Zenable onboarding — discover the standards a codebase already has written down, mine them into candidate requirements, triage them with the user, and persist the survivors as scoped Zenable requirements through the Zenable MCP. Use this skill whenever the user wants to onboard a codebase onto Zenable, set up custom requirements/guardrails for a project, or invokes /z:setup. Also trigger for phrases like "onboard this repo to Zenable", "set up Zenable requirements for this codebase", or "get Zenable guardrails going here".
Fetch and address unresolved Zenable AI guardrails review comments on the current pull request (GitHub PR) or merge request (GitLab MR). Use this skill whenever the user says "triage", "address PR feedback", "fix review comments", "respond to the guardrails bot", or anything about responding to automated code review feedback on a pull/merge request. Also trigger when the user invokes /z:triage.