Use when a repository wants stage-aware cybersecurity guidance during planning, risky implementation changes across authentication, authorization, tokens, secrets, middleware, outbound requests, file handling, CI, deployment, and other trust boundaries, post-implementation review, or pre-release hardening; do not trigger for doc-only, naming-only, formatting-only, or UI-only changes that do not affect a trust boundary

2026-04-0437

sentinelx-review-gate

alicankiraz1/SentinelXPrime

Use when implementation is complete or review is requested and the user may want a focused security review of the changed code

2026-04-0437

using-sentinelx

alicankiraz1/SentinelXPrime

Use when a session needs quick orientation to SentinelXPrime stages, checkpoints, guardrails, and the right SentinelXPrime skill to invoke

2026-04-0437

Fonte

alicankiraz1

alicankiraz1/SentinelXPrime

Abrir repositório GitHub Ver repositórios do creator

Comando de instalação

Download

Executar no Manus

Útil paraSOC

Analistas de segurança da informaçãoInformática e Matemática15-1212L4

name	sentinelx-test-rig
description	Use when a feature or project is nearing handoff or release and the user may want a stack-aware security check plan without automatic setup

Security Test Rig

Overview

Offer a recommendation-only security check plan after implementation. This skill helps users set up the next validation step without silently provisioning anything.

When to Use

a feature or project is approaching release or handoff
the user wants a lightweight hardening or validation pass
the next useful step is tool selection rather than source review

Workflow

Ask once whether the user wants a stack-aware security check plan, following ../sentinelx-prime/references/interaction-model.md for language behavior when available.
If the user declines, stop and do not repeat the same offer in the same stage.
If the user accepts, load references/tool-selection.md and references/sample-commands.md.
Recommend tools, commands, and checklist items based on the stack.
End the recommendation with a closing coverage note using the shared headings: Reviewed / Not reviewed / Assumptions / Tools run.
State clearly that no environment was provisioned and no tooling was installed automatically.

Guardrails

Recommendation-only in v1.
No installation, config mutation, CI wiring, or environment provisioning.
Avoid presenting optional tools as mandatory without context.
Do not hardcode a fixed English ask prompt in this skill.