straymark-status

Identify recently updated StrayMark documentation artifacts and source changes lacking coverage.

2|Updated Apr 2, 2026

Search Tags:#complexity analysis #governance #git log #straymark #documentation compliance #code change auditing

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents undocumented or incompletely documented work by showing which StrayMark artifacts and source changes are missing or newly created after recent development activity.

Core Features & Use Cases

Audits recent documentation: Detects StrayMark documents modified within the last hour across multiple types (AILOG, AIDEC, ADR, ETH, REQ, TES, INC, TDE, SEC, MCARD, SBOM, DPIA) using expected filename prefixes and directory mappings.
Connects code changes to documentation needs: Identifies modified source files and flags likely missing documentation based on code complexity and change category (security, architecture, AI/ML, dependencies, privacy, tests, incidents).
Guides next actions without editing: Summarizes gaps and reminds you to use the appropriate StrayMark creation commands for undocumented changes.

Quick Start

Ask the assistant to run the straymark-status skill to review the last hour of StrayMark activity and highlight modified files that likely require new documentation.

Frequently Asked Questions about straymark-status

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

FAQPage Schema

How do I check for missing documentation after recent code changes?▼

You can verify documentation compliance by running a status check that identifies recently modified source files and flags likely missing documentation based on code complexity and change categories like security, architecture, or AI/ML.

What is a StrayMark documentation compliance audit?▼

A StrayMark documentation compliance audit identifies which documentation artifacts were created or updated recently and which recent source changes lack corresponding records across requirements, decisions, ADRs, ethical reviews, and security assessments.

How do I find recently modified ADR and security assessment files?▼

You can find recently modified ADR and security assessment files by scanning expected filename prefixes and directory mappings to detect StrayMark documents modified within a specific timeframe, using git-based discovery or file modification times as a fallback.

Does the documentation compliance check use git history to find gaps?▼

Yes, the documentation compliance check uses git-based discovery to find gaps when available, applying git log analysis to connect code changes to documentation needs, with a fallback to file modification times if git is unavailable.

Can I automatically generate missing ADRs and ethical reviews during a code audit?▼

No, you cannot automatically generate missing ADRs and ethical reviews during a code audit, because the compliance check reports gaps and actionable recommendations without creating or modifying any files.