doc-sectest-reviewer

Perform semantic quality review for SECTEST artifacts beyond structural validation.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "doc-sectest-reviewer" with this command: npx skills add vladm3105/aidoc-flow-framework/vladm3105-aidoc-flow-framework-doc-sectest-reviewer

doc-sectest-reviewer

Purpose

Perform semantic quality review for SECTEST artifacts beyond structural validation.

Review Scope

  • SEC and SPEC alignment for security requirements

  • Category completeness ([AuthN] , [AuthZ] , [Input] , [Crypto] , [Config] , [Session] )

  • Threat scenario realism and security control completeness

  • Compliance mapping completeness (for example OWASP/CWE/NIST where documented)

  • Safety constraint presence and unsafe-guidance exclusion

  • Traceability completeness and consistency

Safety Policy

  • Security tests must run in isolated environments only.

  • Never run security tests against production systems.

  • Any guidance enabling operational misuse, production-targeted testing, or exploit execution steps is manual_required or blocked .

Output Contract

Reviewer-native output:

  • SECTEST-NN.R_review_report_vNNN.md

Audit-wrapper compatibility:

  • doc-sectest-audit may emit SECTEST-NN.A_audit_report_vNNN.md as preferred fixer input.

All reports are colocated with parent SECTEST file.

Score Gate

  • Pass target: score >=90

  • Manual-required findings block automated completion.

Related Skills

  • doc-sectest-validator

  • doc-sectest-fixer

  • doc-sectest-audit

  • doc-sectest-autopilot

Version History

Version Date Changes

1.0 2026-02-27 Initial SECTEST reviewer with audit-compatible report contract, safety policy, and threshold-based pass gate

Implementation Plan Consistency (IPLAN-004)

  • Treat plan-derived outputs as valid source mode and verify intent preservation from implementation plan scope/objectives.

  • Validate upstream autopilot precedence assumption: --iplan > --ref > --prompt .

  • Flag objective/scope conflicts between plan context and artifact output as blocking issues requiring clarification.

  • Do not introduce legacy fallback paths such as docs-v2.0/00_REF .

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

n8n

No summary provided by upstream source.

Repository SourceNeeds Review
General

google-adk

No summary provided by upstream source.

Repository SourceNeeds Review
General

doc-prd

No summary provided by upstream source.

Repository SourceNeeds Review
General

mermaid-gen

No summary provided by upstream source.

Repository SourceNeeds Review