openclaw-security

Run OpenClaw security audits on code changes before PR submission.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill openclaw-security-pkuppens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-security
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/openclaw-security
Command: npx skills add https://github.com/pkuppens/pkuppens --skill openclaw-security-pkuppens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces OpenClaw security constraints and mandates security audit before every code-change PR. Use when working on OpenClaw projects, before opening a PR, or when configuring or hardening OpenClaw.

Core Features & Use Cases

  • Mandatory PR security audit: Every code-change PR must include a passing OpenClaw security audit.
  • Governance integration: Aligns with quality gates and other skills to ensure audits are completed prior to integration.
  • Remediation guidance: Provides steps to fix issues and re-run audits until success.

Quick Start

Before opening a PR, run openclaw security audit --deep and openclaw security audit --fix until both complete successfully.

Frequently Asked Questions about openclaw-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security audit before opening a pull request?

A mandatory security audit for a pull request validates your code's security posture by running repeatable audit commands that must pass before merging. It enforces security hygiene by checking code changes against OpenClaw security constraints.

How do I enforce a mandatory security audit on every code-change PR?

You enforce a mandatory security audit on every code-change PR by integrating this Skill into your pull request workflow. It runs OpenClaw security audits on code changes and requires explicit, repeatable audit commands to pass before merging.

What steps should I follow to remediate security audit failures?

To remediate security audit failures, follow the provided remediation guidance to fix identified issues, then re-run the openclaw security audit commands until they complete successfully before opening your pull request.

Does the security audit apply to deployment configurations and tool integrations?

Yes, the security audit applies to PR workflows, deployment configurations, and tool integrations across OpenClaw projects. It validates security posture across all these components before merging code changes.

Can I integrate the security audit with existing governance and quality gates?

Yes, the security audit integrates with quality gates and governance skills to ensure audits are completed prior to integration. It aligns with other skills to enforce security constraints before a pull request is merged.

When should I not rely solely on automated security audit fixes?

You should not rely solely on automated fixes when the audit --fix command cannot resolve complex compliance or governance issues. In such cases, manual remediation is required, and you must re-run the deep audit until it passes.