Fähigkeiten nestjs-feature-audit

📦

nestjs-feature-audit

Name: nestjs-feature-audit
Author: amirtaherkhani

v1.0.2 Inhaltsrevision r1 Sicher ⚙️ Externe Befehle

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.

Unterstützt: Claude Codex Code(CC)

🥉 78 Bronze

Maintain this Skill? Claim it 🥉 78 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/amirtaherkhani-nestjs-feature-audit.md Signiertes manifest GET /api/skills/amirtaherkhani-nestjs-feature-audit/manifest Signiertes lockfile GET /api/skills/amirtaherkhani-nestjs-feature-audit/lockfile

Testen

„nestjs-feature-audit“ wird verwendet. Audit a feature with verified validation, missing retry logic, an active legacy adapter, and an unauthorized production cutover.

Erwartetes Ergebnis:

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.

„nestjs-feature-audit“ wird verwendet. Audit invoice-reminders when documentation contains only a feature mention without acceptance conditions.

Erwartetes Ergebnis:

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.

Sicherheitsaudit

Sicher

v1 • 4.10.2026 Versionsbericht öffnen

All 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.

Gescannte Dateien

428

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Risikofaktoren

⚙️ Externe Befehle (34)

Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/amirtaherkhani-nestjs-feature-audit/security.svg)](https://skillstore.io/skills/amirtaherkhani-nestjs-feature-audit?utm_source=security_passport_badge)

HTML-Badge

<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>

Einbettungskarte

<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>

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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/1

BibTeX-Zitat

@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"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

100

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

Audit One Feature

Audit the payments feature against its documented roadmap on main. Return the evidence-backed report without implementing fixes.

Review a Release Branch

Audit subscriptions on branch release/subscriptions against the documented acceptance plan. Record revision freshness and cite evidence for each requirement. Do not implement fixes.

Assess a Migration

Audit internal-events against its migration roadmap on main. Separate replacement code, active legacy paths, and production cutover prerequisites. Report exit evidence without deploying.

Build Detailed Acceptance Traceability

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.

Bewährte Praktiken

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.

Vermeiden

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.

Häufig gestellte Fragen

What does this skill require?

It requires Git, a NestJS repository, a feature name, and a clear roadmap. Remote updates also require network access.

What happens when no roadmap is available?

It reports searched paths and terms, rejects unclear candidates, and asks for a roadmap before classifying implementation.

Can I supply the roadmap directly?

Yes. A user-supplied roadmap can satisfy the gate when it identifies the feature and defines concrete requirements or acceptance conditions.

Does the audit change Git state?

An explicit invocation authorizes remote fetch, branch switching, and fast-forward preparation when safe. Dirty, detached, or in-progress states stop automatic preparation.

Will it fix findings or deploy the feature?

No. Fixes require explicit authorization and a separate implementation phase. Publication, deployment, and roadmap edits require their own authorization.

Can I use it with Claude, Codex, and Claude Code?

The skill declares support for all three. Use the installed skill interface; slash-command aliases depend on host configuration.