verify-changes — community verify-changes, finserv-webinar, community, ide skills

v1.0.0

About this Skill

Perfect for Code Review Agents needing automated PII compliance checks and security scans. Runs comprehensive verification on code changes. Triggers when user says verify my changes, check my work, run verification, validate changes, or QA check.

hgchrre hgchrre
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
48
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing automated PII compliance checks and security scans. Runs comprehensive verification on code changes. Triggers when user says verify my changes, check my work, run verification, validate changes, or QA check.

Core Value

Empowers agents to run parallel verification tasks, including PII compliance checks with masking and audit logging analysis, and security scans using Snyk scans for source vulnerabilities, ensuring secure code deployment.

Ideal Agent Persona

Perfect for Code Review Agents needing automated PII compliance checks and security scans.

Capabilities Granted for verify-changes

Automating code validation for secure deployment
Running parallel PII compliance checks and security scans
Validating changes before committing or deploying code

! Prerequisites & Limits

  • Requires Snyk API access for security scans
  • Limited to code repositories with accessible file systems

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is verify-changes?

Perfect for Code Review Agents needing automated PII compliance checks and security scans. Runs comprehensive verification on code changes. Triggers when user says verify my changes, check my work, run verification, validate changes, or QA check.

How do I install verify-changes?

Run the command: npx killer-skills add hgchrre/finserv-webinar/verify-changes. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for verify-changes?

Key use cases include: Automating code validation for secure deployment, Running parallel PII compliance checks and security scans, Validating changes before committing or deploying code.

Which IDEs are compatible with verify-changes?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for verify-changes?

Requires Snyk API access for security scans. Limited to code repositories with accessible file systems.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add hgchrre/finserv-webinar/verify-changes. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use verify-changes immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

verify-changes

Install verify-changes, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Change Verification

Run all 4 verification agents in parallel to validate changes before committing or deploying.

Agents (run in parallel)

1. PII Compliance Checker

Task: pii-compliance-checker
Prompt: "Review the recently changed files for PII handling violations.
        Check: masking, audit logging, data leaks in console/errors."

2. Security Scanner

Task: security-scanner  
Prompt: "Run Snyk scans on the project.
        - snyk_code_scan for source vulnerabilities
        - snyk_sca_scan for dependency vulnerabilities
        Report critical/high findings."

3. Verifier

Task: verifier
Prompt: "Verify the implementation is complete and functional.
        Check: no broken imports, no TODO placeholders, UI renders correctly."

4. Test Runner

Task: Test Runner
Prompt: "Run the test suite. If tests fail, report which tests failed and why.
        Do not auto-fix unless explicitly asked."

Output

Combine results into a verification report:

markdown
1## Verification Report 2 3| Check | Status | Findings | 4|-------|--------|----------| 5| PII Compliance | ✅/⚠️/❌ | [summary] | 6| Security | ✅/⚠️/❌ | [summary] | 7| Implementation | ✅/⚠️/❌ | [summary] | 8| Tests | ✅/⚠️/❌ | [pass/fail count] | 9 10### Issues to Address 111. [Issue from any failing check] 122. [Issue from any failing check] 13 14### Ready to Commit: Yes/No

Related Skills

Looking for an alternative to verify-changes or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer