Verified:Website 𝕏@StrangeDaysTech GitHub

straymark-audit-prompt

Generate a unified audit prompt from Charter context to a canonical file path.

2|Updated Apr 2, 2026

Search Tags:#prompt generation #git diff #evidence citation #charter audits #multi-auditor orchestration #governance checkpoint

Ready to run

npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-audit-prompt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: straymark-audit-prompt
Source: https://github.com/StrangeDaysTech/arborist-cli/tree/main/.gemini/skills/straymark-audit-prompt
Command: npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-audit-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of manually collecting Charter context and assembling a consistent audit instruction set for multiple auditors by generating the unified audit prompt at the canonical on-disk location.

Core Features & Use Cases

Unified prompt generation from Charter context: Resolves the Charter and produces a self-contained audit prompt that embeds the Charter content, originating AILOGs, relevant git diff, and discipline rules (including SOLO LECTURA and evidence-citation/severity calibration).
Orchestration for multi-auditor workflows: Prepares the prompt once so multiple auditor-side CLIs can read it from disk, avoiding copy/paste drift and ensuring consistency across model sessions.
CI/checkpoint-oriented usage: Supports the audit checkpoint flow for Charters in in-progress or declared status, with a surfaced warning when status is closed.

Quick Start

Run the audit prompt preparation for a Charter by executing: straymark charter audit <CHARTER-ID> --prepare.

Frequently Asked Questions about straymark-audit-prompt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a unified audit prompt for a Charter from git diff and AiLOGs?▼

To generate a unified audit prompt, run the preparation command for your Charter ID with the prepare flag. This resolves the Charter status and embeds the Charter content, AiLOGs, git diff, and discipline rules into a single self-contained audit prompt file on disk.

What is the best way to prepare audit prompts for multiple auditors without copy/paste drift?▼

The best way to prevent copy/paste drift across multiple auditors is to generate a single canonical audit prompt file on disk. Auditor-side CLIs can then read this unified instruction set directly from the filesystem, ensuring consistent context across all model sessions.

How do I resolve placeholder content for a Charter audit checkpoint workflow?▼

You can resolve preparation-only placeholder content by executing the charter audit command with the prepare flag. This resolves the Charter status and generates the complete audit prompt without requiring operator intervention or manual copy/paste.

Can I run audit prompt preparation on a Charter that is already closed?▼

You should not run audit prompt preparation on a closed Charter. The workflow applies to Charters in in-progress or declared status; if the Charter is closed, the system will surface a warning indicating that the audit checkpoint process is not applicable.

Where does the generated audit prompt file get written on the filesystem?▼

The generated audit prompt file is written to a canonical filesystem directory specific to the Charter ID. Targeting this standard path allows multiple auditor-side CLIs to automatically locate and consume the same embedded Charter, AiLOG, and git diff instructions.

Does the generated audit prompt include evidence citation and severity calibration rules?▼

Yes, the generated audit prompt embeds discipline rules including SOLO LECTURA and evidence-citation/severity calibration. This ensures that all auditors consuming the prompt apply the same governance and compliance standards during the Charter audit checkpoint.