← all publishers

wazuh

@wazuh source repo

Report this profile Claim this profile

• 9 skills
• 0 followers
• 9 hours ago last updated

1. ▌
   Docs Review · wazuh bundle

   Audit the wazuh-indexer-plugins mdBook documentation (docs/) for coverage gaps, staleness against source code, structural/navigation issues, and style inconsistency. Produces a written findings report — it does not rewrite prose. Use when asked to review, audit, or assess the Wazuh Indexer technical documentation.
   0
   installs
2. ▌
   Perf Tuning · wazuh bundle

   Reduce or validate Wazuh Indexer 5.0's memory/CPU/GC footprint by tuning existing OpenSearch/plugin settings, or by changing index/shard topology. Covers the settings catalog (content-manager, security-analytics, alerting, setup, OpenSearch core), the Docker load-test harness and the real vagrant VM, one-variable-at-a-time attribution methodology, and known traps (detector fan-out, the SAP dedicated-query-index dead end, unbounded queues). Use when asked to investigate, reduce, or test Wazuh Indexer memory usage, heap pressure, circuit breaker trips, or shard/index count, or to tune throughput-vs-memory tradeoffs.
   0
   installs
3. ▌
   Wcs Management · wazuh bundle

   Maintain and create Wazuh Common Schema (WCS) modules under wcs/ in wazuh-indexer-plugins. Use when asked to add a field to a WCS module, change a module's index/template settings, create a new WCS module, or regenerate WCS index templates. Covers the module anatomy, the ECS-subset + custom-field YAML dialect, the 3-step Docker generator pipeline (update_module_list.sh, generate_schema.sh, count_and_update_total_fields.sh), and the out-of-tree wiring (SetupPlugin.java, module_list). Never hand-edit generated templates.
   0
   installs
4. ▌
   Create Pr · wazuh

   Prepare a standardized pull request for a Wazuh Dashboard repository (verify version base branch, DCO sign-off, CHANGELOG entry, run local checks, and produce a ready-to-paste PR body with a pre-flight report). By default it prepares and hands off; it only runs `gh pr create` when explicitly asked. Use when the user asks to create, open, draft, or prepare a PR, or to get work ready for review.
   0
   installs
5. ▌
   Resolve Cve · wazuh

   Resolve a dependency CVE in the Wazuh Dashboard alerting plugin — confirm the vulnerable package is actually present and reachable, apply the least-invasive remediation (direct bump, lockfile dedupe, or scoped resolution), verify build/tests/audit, and hand off a prepared PR. Use when the user asks to fix or resolve a CVE / dependency vulnerability, or provides a CVE id or CVE issue URL.
   0
   installs
6. ▌
   Develop Issue · wazuh

   Implement a GitHub issue end-to-end in a Wazuh Dashboard repo — plan, code following repo conventions, add colocated tests, validate with check-standards, add the CHANGELOG entry, and deliver a filled PR-template body (leaving Results and Evidence/screenshot to the developer) WITHOUT opening the PR. Use when the user provides an issue to develop, implement, or work on.
   0
   installs
7. ▌
   Issue Creation · wazuh

   Create a well-formed GitHub issue in a Wazuh Dashboard repo — pick the right issue template, run an issue-first duplicate check, and produce a ready-to-file body with the template's default labels. Use when the user asks to create, open, file, or draft an issue.
   0
   installs
8. ▌
   Check Standards · wazuh

   Run the same code-quality checks CI runs (Prettier format, ESLint, typecheck, and unit tests) over the current diff before pushing or marking a PR ready. Use before opening/updating a PR, when the user asks to verify standards, lint, format, or check that CI will pass.
   0
   installs
9. ▌
   Analyze Dashboard Vuln · wazuh

   Analyze a Wazuh dashboard vulnerability row, decide whether the affected library is reachable in production, fill the sheet's CVSS-Overall→Notes columns, and draft a GitHub issue body. User-invoked. Use when triaging Artifactory CVE rows across the Wazuh dashboard repos, before remediation.
   0
   installs