00_workspace_forensics_skill

This skill generates a complete workspace profile with git signals and build configs, enabling downstream tools to verify forensics completeness.
  • PowerShell

20

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill sounder25/google-antigravity-skills-library --skill 00_workspace_forensics

  • audit_workspace.ps112.5 KB
  • skill.md3.5 KB

Overview

This skill generates a comprehensive workspace profile that captures git signals, build configurations, language detection, and forensics completeness tracking. It produces a machine-readable WORKSPACE_PROFILE.json and a human-readable FORENSICS_SUMMARY.md to serve as the canonical source of workspace facts. Other workspace operations should consume this profile or refuse to run without it.

How this skill works

The audit scans the given workspace path, validates access and environment prerequisites, and collects repository metadata, git status and commit history, detected languages, build and test commands, intent breadcrumbs, and code markers (TODO/FIXME/HACK). Outputs include a detailed JSON profile and a summary markdown with recommendations. The tool respects .gitignore, limits recursion, and performs read-only git operations where available.

When to use it

  • Before running any automated code-modifying agent or meta-skill
  • During onboarding of a new repository to establish baseline signals
  • When diagnosing build failures or flaky CI by collecting reproducible context
  • Prior to vulnerability scans or security reviews to capture current state
  • When tracking forensics completeness for audits or postmortems

Best practices

  • Run the audit from repository root or explicitly provide --workspace-path
  • Use --output-dir to centralize artifacts (default: ./.forensics) and commit WORKSPACE_PROFILE.json if policy allows
  • Ensure Git is installed and available to collect full git_signals; tool degrades gracefully if missing
  • Prefer PowerShell Core 7+ for cross-platform consistency; PowerShell 5.1 is supported on Windows
  • Verify forensics_completeness is 'full' before allowing downstream automated changes

Example use cases

  • Generate WORKSPACE_PROFILE.json before a large refactor so other skills use consistent repository facts
  • Collect build and test commands to bootstrap CI configuration or reproduce local failures
  • Create an audit snapshot prior to an adversarial review or safety gate execution
  • Produce a human-readable forensics summary to brief reviewers or auditors
  • Integrate into pre-action guards to halt unsafe operations when profile collection is incomplete

FAQ

The audit runs and marks git_signals as partial or absent; collection proceeds with file-system and build signal gathering, and results indicate missing git evidence.

Can I change the output format or location?

Yes. Use --output-format (json, md, both) and --output-dir to specify where artifacts are written.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
00_workspace_forensics skill by sounder25/google-antigravity-skills-library | VeilStrat