organvm-iv-taxis/workspace-autopsy-governance
distributions/claude/skills/workspace-autopsy-governance/SKILL.md
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
$ install --global
skillsauthnpx skillsauth add organvm-iv-taxis/a-i--skills workspace-autopsy-governanceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 2:13 AM129.3s7 files scanned
SKILL.md
- name:
- workspace-autopsy-governance
- description:
- Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
- license:
- MIT
Workspace Autopsy & Governance Restructure
Overview
This skill enables agents to systematically analyze (autopsy) an existing, potentially disorganized workspace, propose a logical new directory structure, and migrate the workspace to this new structure while enforcing new governance standards.
Workflow
To execute this skill, follow these sequential steps:
Phase 1: Workspace Autopsy (Mapping)
To begin, you must understand the current state of the workspace.
- Run the autopsy script to map the directory:
python /Users/4jp/.agents/skills/workspace-autopsy-governance/scripts/workspace_autopsy.py --dir . - Review the generated map and statistics. Identify:
- Where the core source code lives.
- Where documentation, scripts, and assets are currently scattered.
- Legacy folders or structural chaos that need cleaning.
Phase 2: Sending the Signal (Restructure Proposal)
Before moving any files, you must "send out the signal" to the user proposing the new structure and governance.
- Read the template from
assets/RESTRUCTURE_PROPOSAL-template.md. - Draft a customized
RESTRUCTURE_PROPOSAL.mdbased on your findings from the autopsy. Detail exactly which directories will be created and which files will move where. - Present this proposal to the user and wait for their explicit approval. Do not proceed to Phase 3 without approval.
Phase 3: Unite Under New Locations (Migration)
Once the user approves the proposal:
- Create the new target directories (e.g.,
/src,/docs,/scripts,/assets,/tests) as agreed upon in the proposal. - Use standard shell commands (
mv) to systematically migrate files from their old locations to the newly created, unified locations. - Ensure no orphaned files remain in chaotic root locations unless they are standard configuration files (e.g.,
.gitignore,package.json).
Phase 4: Establish New Governance
With the files in their new locations, establish the rules that will govern them going forward.
- Read the template from
assets/GEMINI-template.md. - Customize it to reflect the specific standards, workflows, and constraints of the newly restructured project.
- Write this customized governance document to
GEMINI.mdat the root of the project. - If appropriate, create subdirectory-specific
GEMINI.mdfiles for deeper governance (e.g., in/src/GEMINI.md).
Resources Included
scripts/workspace_autopsy.py
A Python script that traverses the specified directory, ignores common build/dependency folders, and prints a tree map along with statistics about file types and counts.
assets/RESTRUCTURE_PROPOSAL-template.md
A template for the document you will generate to propose the new structure to the user.
assets/GEMINI-template.md
A template for the governance rules to establish in the repository after the restructure.
Related Skills
organvm-iv-taxis/shell-history-hygiene
development
VerifiedTrustedCommunity
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/setup-cowork
tools
VerifiedTrustedCommunity
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-lifecycle-patterns
development
VerifiedTrustedCommunity
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
12SKILL.mdUpdated Jul 20, 2026
organvm-iv-taxis/session-governance-audit
tools
VerifiedTrustedCommunity
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.
12SKILL.mdUpdated Jul 20, 2026