seis-security-review

Review SEIS repository changes for secrets, least-privilege, SSH hardening, and validation-claim risks.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-security-review-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-security-review
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis/skills/seis-security-review
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-security-review-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews of repository changes often miss leaked secrets, over-privileged access, non-idempotent hardening scripts, and unverified claims that code was deployed, merged, or protected. This Skill provides a structured review workflow that catches these risks before they reach production. ## Core Features & Use Cases - Secret and Credential Detection: Blocks private keys, API keys, inline passwords, token assignments, and copied .env values before they enter the repository. - Least-Privilege and Hardening Review: Inspects users, tokens, GitHub workflow permissions, SSH access, firewall scope, and cloud service accounts, requiring idempotent and rollback-ready hardening scripts. - Validation Honesty Enforcement: Prevents unverified claims of pushed, merged, deployed, connected, ready, protected, or hardened states without direct evidence from commands, GitHub, or cloud providers. - Use Case: Before merging a PR that modifies SSH hardening scripts and GitHub workflows, run this review to confirm no secrets are committed, firewall rules are idempotent, rollback steps are documented, and branch protection claims are backed by actual GitHub state. ## Quick Start Use the seis-security-review skill to audit my current pull request for leaked secrets, least-privilege violations, and unverified deployment claims.

Frequently Asked Questions about seis-security-review

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

FAQPage Schema
How do I review a pull request for leaked secrets and credentials?▼

Check secret safety before functionality by scanning for private keys, API keys, inline passwords, token assignments, and copied .env values. Reject any change containing credentials or sensitive infrastructure details before evaluating the rest of the code.

How to verify SSH hardening scripts are safe to rerun?▼

Check idempotency by confirming the script avoids duplicated config lines, conflicting firewall rules, and partial state when rerun. Require documented rollback and recovery steps before any destructive, network, SSH, or firewall operation.

What checks should run before claiming a change is deployed or protected?▼

Require direct evidence from the relevant local command, GitHub state, cloud provider state, or an explicit maintainer waiver. Suggested checks include npm run check:seis-master-prompt, check:open-source-governance, and quality, plus the SSH manager unittest path when it exists.

When should a security review block a merge or deployment?▼

Block and request explicit maintainer approval before destructive operations, deploy, merge, push, history rewrite, firewall lockout risk, live SSH changes, or any action that could expose secrets or block access.

Does this review cover GitHub workflow and CODEOWNERS changes?▼

Yes, it inspects GitHub workflow permissions, CODEOWNERS, branch protection claims, and governance files. It requires GitHub evidence before accepting claims about branch protection, required checks, or release readiness.