Feat Audit

Name: Feat Audit
Author: pwdev-solucoes

ASecurity

Use when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions, artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to enable the audit (feat-init) or for plan status (feat-status).

3 stars

0 votes

0 copies

0 views

Added 9/28/2026

databasespythonsqldatabase

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/28/2026

$npx -y skills add pwdev-solucoes/pwdev-claude-marketplace --skill feat-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Feat Audit?

Add the live security badge to your README — it updates automatically with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pwdev-solucoes-feat-audit/badge)](https://www.skillsdirectory.com/skills/pwdev-solucoes-feat-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

Files

SKILL.md

---
name: feat-audit
description: >
  Use when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de
  auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions,
  artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to
  enable the audit (feat-init) or for plan status (feat-status).
metadata:
  version: 3.2.1
---

# Audit trail

Schema and recording model: `references/audit-schema.md`. The database is shared with other
PWDEV plugins; filter with `--plugin pwdev-feat` when the human wants only this plugin.

## Procedure

1. **Language** — resolve `lang` (`references/language.md`).
2. Map the argument to one command and run it from the project root:

   | Argument | Command |
   |---|---|
   | (empty) / `summary` | `python3 "<plugin-root>/scripts/audit.py" summary` |
   | `events [plugin]` | `... events [--plugin <plugin>] [--limit N]` |
   | `decisions` / `artifacts` / `stats` | `... decisions` / `... artifacts` / `... stats` |
   | `export` | `... export --pdf` (Markdown always; PDF only when pandoc exists) |
   | `query <SQL>` | `... query "<SQL>"` |

3. Exit 2 (`AUDIT_DISABLED` / `AUDIT_DB_MISSING`) → tell the human to enable it with
   `feat-init`. Exit 1 (`REJECTED` / `SQL_ERROR`) → show the message; only a single
   read-only SELECT is accepted and the database is opened read-only.
4. Present the Markdown output as is, translating only the headings when `lang` is `pt-BR`.
   Unknown argument → list the commands above.

Never write to the audit database from this skill.

Language: resolve `lang` per `references/language.md` before any human-facing output. Safety: never read or expose `.env*` (except `.env.example`/`.template`/`.sample`), keys, certificates or credentials — `references/safety.md`. Paths `references/`, `scripts/`, `templates/`, `schemas/` are relative to the plugin root (`references/runtime.md`).

Attribution

pwdev-solucoes

View source See grades on GitHub More from pwdev-solucoes →

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

--- name: feat-audit description: > Use when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions, artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to enable the audit (feat-init) or for plan status (feat-status). metadata: version: 3.2.1 --- # Audit trail Schema and recording model: `references/audit-schema.md`. The database is shared with other PWDEV plugins; filter with `--plugin pwdev-feat` when the human wants only this plugin. ## Procedure 1. **Language** — resolve `lang` (`references/language.md`). 2. Map the argument to one command and run it from the project root: | Argument | Command | |---|---| | (empty) / `summary` | `python3 "<plugin-root>/scripts/audit.py" summary` | | `events [plugin]` | `... events [--plugin <plugin>] [--limit N]` | | `decisions` / `artifacts` / `stats` | `... decisions` / `... artifacts` / `... stats` | | `export` | `... export --pdf` (Markdown always; PDF only when pandoc exists) | | `query <SQL>` | `... query "<SQL>"` | 3. Exit 2 (`AUDIT_DISABLED` / `AUDIT_DB_MISSING`) → tell the human to enable it with `feat-init`. Exit 1 (`REJECTED` / `SQL_ERROR`) → show the message; only a single read-only SELECT is accepted and the database is opened read-only. 4. Present the Markdown output as is, translating only the headings when `lang` is `pt-BR`. Unknown argument → list the commands above. Never write to the audit database from this skill. Language: resolve `lang` per `references/language.md` before any human-facing output. Safety: never read or expose `.env*` (except `.env.example`/`.template`/`.sample`), keys, certificates or credentials — `references/safety.md`. Paths `references/`, `scripts/`, `templates/`, `schemas/` are relative to the plugin root (`references/runtime.md`).