nestjs-feature-audit
Audit NestJS Features Against Their Roadmaps
Source code alone cannot establish whether a NestJS feature satisfies its roadmap. This skill compares requirements with revision-specific evidence and reports completed work, gaps, legacy paths, bugs, and blockers.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "nestjs-feature-audit" from https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit.md and its manifest at https://skillstore.io/api/skills/amirtaherkhani-nestjs-feature-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "nestjs-feature-audit". Audit a feature with verified validation, missing retry logic, an active legacy adapter, and an unauthorized production cutover.
Resultado esperado:
- Illustrative verdict: incomplete, with a separate rollout blocker.
- Implemented: request validation is wired and supported by a passing acceptance check.
- Missing/Not Implemented: required retry behavior is absent from the inspected integration points.
- Legacy Code: the old adapter remains active although the roadmap requires replacement.
- Bugs & Blockers: production cutover requires authorization and live acceptance evidence.
- Each real report item includes requirement citations, observed evidence, impact, and the next validation step.
Usando "nestjs-feature-audit". Audit invoice-reminders when documentation contains only a feature mention without acceptance conditions.
Resultado esperado:
- Roadmap required for invoice-reminders before the audit can continue.
- The feature mention does not define concrete outcomes or acceptance conditions.
- The response lists the actual documentation paths, search terms, and rejected candidates.
- Provide a roadmap file or its contents. Implementation status is not classified until the roadmap gate passes.
Auditoría de seguridad
SeguroAll 35 static findings are false positives: Markdown backticks were mistaken for execution, and a reporting heading was mistaken for system reconnaissance. No evidence found of prompt injection, data exfiltration, or malicious intent in the reviewed files. The workflow includes remote fetch, branch switching, and fast-forward updates, with explicit worktree safeguards and no automatic fixes or publication.
Factores de riesgo
⚙️ Comandos externos (34)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/amirtaherkhani-nestjs-feature-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/amirtaherkhani-nestjs-feature-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
amirtaherkhani. (2026). nestjs-feature-audit security audit report (audit version 1) [Author version 1.0.2]. Skillstore. https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit/audits/1Cita BibTeX
@techreport{amirtaherkhani-amirtaherkhani-nestjs-feature-audit-2026,
author = {amirtaherkhani},
title = {nestjs-feature-audit security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit/audits/1},
note = {Author version 1.0.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nestjs-feature-audit security audit report (audit version 1)"
version: "1.0.2"
type: report
authors:
- name: "amirtaherkhani"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit/audits/1"
identifiers:
- type: other
value: "skillstore:amirtaherkhani-nestjs-feature-audit:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Check Release Readiness
Compare a feature on a release branch with its acceptance plan and identify missing evidence before approval.
Review Migration Progress
Identify active legacy paths, replacement coverage, and rollout prerequisites against a documented migration roadmap.
Plan Acceptance Validation
Map roadmap requirements to tests and observed behavior, then list the checks needed to resolve unverified items.
Prueba estos prompts
Audit the payments feature against its documented roadmap on main. Return the evidence-backed report without implementing fixes.
Audit subscriptions on branch release/subscriptions against the documented acceptance plan. Record revision freshness and cite evidence for each requirement. Do not implement fixes.
Audit internal-events against its migration roadmap on main. Separate replacement code, active legacy paths, and production cutover prerequisites. Report exit evidence without deploying.
Audit refunds on branch release/refunds using the attached roadmap as the authoritative target. Trace each acceptance condition across source, wiring, tests, configuration, and available runtime evidence. Deduplicate findings and identify next validation steps. Do not mutate implementation or publish changes.
Mejores prácticas
- Name the feature, target branch, and authoritative roadmap before requesting comparison.
- Keep the worktree clean and approve any local-snapshot exception explicitly when remote freshness cannot be verified.
- Review each requirement citation and next-proof step before treating implemented source as production completion.
Evitar
- Treating a TODO mention or existing source code as the feature roadmap.
- Interpreting unavailable tests, missing runtime access, or unperformed deployment checks as verified success.
- Using an audit request as permission to implement fixes, publish changes, or deploy.
Preguntas frecuentes
What does this skill require?
What happens when no roadmap is available?
Can I supply the roadmap directly?
Does the audit change Git state?
Will it fix findings or deploy the feature?
Can I use it with Claude, Codex, and Claude Code?
Detalles del desarrollador
Autor
amirtaherkhaniLicencia
MIT
Versión del autor
v1.0.2
Revisión de Skillstore
r1
Ref.
c97a1862d1bc82763903ee068cd15acab35d638c
Actualidad del mantenimiento
5/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos