web-monitor-safety-check

Validate git diffs against security and operational constraints.

26|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/yjzhang2003/oh-my-feishu --skill web-monitor-safety-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-monitor-safety-check
Source: https://github.com/yjzhang2003/oh-my-feishu/tree/main/workspace/.claude/skills/web-monitor-safety-check
Command: npx skills add https://github.com/yjzhang2003/oh-my-feishu --skill web-monitor-safety-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents dangerous or unauthorized code changes from being merged by enforcing strict safety guardrails on proposed diffs.

Core Features & Use Cases

  • Path Guard: Ensures all modifications remain within the designated repository root to prevent path traversal.
  • Diff Size Guard: Automatically blocks massive changes that exceed 500 lines or 10 files to ensure human review.
  • Secret Scan: Detects and rejects potential hardcoded credentials like API keys or passwords.
  • Use Case: Use this during an automated repair workflow to verify that an AI-generated patch is safe before applying it to your production codebase.

Quick Start

Run the web-monitor-safety-check skill against the current git diff to validate the safety of the proposed changes.

Frequently Asked Questions about web-monitor-safety-check

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

FAQPage Schema
How do I prevent hardcoded secrets and API keys in git diffs?

To prevent hardcoded secrets in git diffs, use automated safety guardrails that scan code modifications to detect and reject potential credentials like API keys or passwords before they are merged.

How do I block large code changes from being merged without human review?

You can block massive code changes by enforcing diff size limits that automatically reject modifications exceeding 500 lines or 10 files, ensuring all substantial changes receive proper human review.

Can I validate AI-generated patches before applying them to production?

Yes, you can validate AI-generated patches by running automated safety checks against the current git diff to verify path boundaries, secret leakage, and test coverage before applying them to production.

What is path traversal prevention in code modification pipelines?

Path traversal prevention in code modification pipelines enforces a path guard that ensures all file modifications remain strictly within the designated repository root to prevent unauthorized file access.

Does this safety check verify test coverage for logic changes?

Yes, the safety check verifies test coverage by ensuring that any logic changes within the proposed diff are accompanied by appropriate tests, maintaining system integrity during automated repair workflows.