メニュー
Show StrayMark documentation status. Use to verify if AI agents properly documented their changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | straymark-status |
| description | Show StrayMark documentation status. Use to verify if AI agents properly documented their changes. |
This skill checks the documentation status of the StrayMark in the current project.
When invoked, perform the following checks and display the results:
Search for StrayMark documents created or modified in the last hour:
# Committed in the last hour
git log --since="1 hour ago" --name-only --pretty=format: -- ".straymark/**/*.md" | sort -u | grep -v "^$"
# PLUS uncommitted StrayMark docs (staged + unstaged + untracked) — this skill runs
# pre-commit, so newly created docs are usually NOT in the git log yet.
git status --porcelain -- ".straymark" | grep '\.md$'
If git is not available or the directory is not a git repo, use file modification times. Check these directories for each document type:
| Type | Prefix | Directory |
|---|---|---|
| AILOG | AILOG- | .straymark/07-ai-audit/agent-logs/ |
| AIDEC | AIDEC- | .straymark/07-ai-audit/decisions/ |
| ADR | ADR- | .straymark/02-design/decisions/ |
| ETH | ETH- | .straymark/07-ai-audit/ethical-reviews/ |
| REQ | REQ- | .straymark/01-requirements/ |
| TES | TES- | .straymark/04-testing/ |
| INC | INC- | .straymark/05-operations/incidents/ |
| TDE | TDE- | .straymark/06-evolution/technical-debt/ |
| SEC | SEC- | .straymark/08-security/ |
| MCARD | MCARD- | .straymark/09-ai-models/ |
| SBOM | SBOM- | .straymark/07-ai-audit/ |
| DPIA | DPIA- | .straymark/07-ai-audit/ethical-reviews/ |
Also enumerate Charters (bounded units of work — distinct from doc types; see STRAYMARK.md §15):
# Charters list with status counts (declared / in-progress / closed)
straymark charter list 2>/dev/null
If the project has no Charters yet but the work clearly fits the trigger (multi-session implementation block, >5 tasks across phases, audit value), surface that as a gap and recommend /straymark-charter-new.
Identify source files that were modified and might need documentation:
# Modified source files in the CURRENT work — label each block.
# Avoid `HEAD~1..HEAD`: it lists the previous commit's files, not current work.
git diff --cached --name-only # staged
git diff --name-only # unstaged
git status --porcelain | awk '/^\?\?/ {print $2}' # untracked
Filter to show only files that might need documentation:
*.md, *.json, *.yml, *.yaml, *.lock, package-lock.json*.ts, *.js, *.tsx, *.jsx, *.py, *.go, *.rs, *.java, *.cs, *.rb, *.phpRun complexity analysis on modified source files:
# Analyze complexity of changed files (primary method for AILOG trigger)
straymark analyze --output json 2>/dev/null
# If CLI unavailable, fall back to line count heuristic in step 3
For each modified source file, check if there's a corresponding StrayMark document:
straymark analyze reports summary.above_threshold > 0; fallback if CLI unavailable: >20 lines of business logic) should have an AILOGpackage.json, Cargo.toml, go.mod, etc.) should have an SBOM.straymark/charters/Format the output as follows:
StrayMark Status
================================================================================
Recent Documents (last hour):
✅ AILOG-2025-01-27-001-implement-auth.md
✅ AIDEC-2025-01-27-001-auth-strategy.md
Modified Files Without Documentation:
⚠️ src/auth/login.ts (cognitive: 12, threshold: 8)
⚠️ src/api/users.ts (cognitive: 9, threshold: 8)
Summary:
Documents created: 2
Files needing review: 2
Use /straymark-new to create documentation for undocumented changes.
Maintain the follow-ups backlog registry — the canonical answer to "what's pending?". Session-start glance, pre-commit drift --apply, post-Charter-close triage (note / set-status), ex-ante creation at Charter declaration (new), and operator-gated promote. Thin wrapper over the straymark followups CLI; never edits CLI-owned counters by hand.
Maintain the follow-ups backlog registry — the canonical answer to "what's pending?". Session-start glance, pre-commit drift --apply, post-Charter-close triage (note / set-status), ex-ante creation at Charter declaration (new), and operator-gated promote. Thin wrapper over the straymark followups CLI; never edits CLI-owned counters by hand.
Execute an external audit of a Charter inside an auditor-side CLI (gemini-cli, claude-cli, copilot-cli, codex-cli). Reads the resolved audit prompt from the canonical location, audits with tool use, writes the report. Operator invokes one instance per CLI.
Generate the unified audit prompt for a Charter at the canonical filesystem location. The operator then opens N auditor-side CLIs (gemini-cli, claude-cli, copilot-cli, etc.) and invokes /straymark-audit-execute in each — no copy/paste. Counterpart of /straymark-audit-review.
Consolidate N external auditor reports into a critical review document with verdicts, remediation plan, and auditor ratings. Then merge the external_audit YAML block into the Charter telemetry. Counterpart of /straymark-audit-prompt and /straymark-audit-execute.
Execute an external audit of a Charter inside an auditor-side CLI (gemini-cli, claude-cli, copilot-cli, codex-cli). Reads the resolved audit prompt from the canonical location, audits with tool use, writes the report. Operator invokes one instance per CLI.