pre-start-context

Load repository and environment context from filesystem configuration and recent commits.

11|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/ruah-dev/ruah-orch --skill pre-start-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-start-context
Source: https://github.com/ruah-dev/ruah-orch/tree/main/.claude/skills/pre-start-context
Command: npx skills add https://github.com/ruah-dev/ruah-orch --skill pre-start-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates uncertainty at task start by automatically discovering a repository's stack, architecture, and state, applying project governance, and loading cross-session memory so agents and workflows start with accurate context and safety guards.

Core Features & Use Cases

  • Repository discovery: Detect runtimes, workspaces, CI, key config files, and architecture patterns across mono- and multi-repo layouts.
  • Governance enforcement: Read .claude/governance.md to apply project-specific rules, sandbox boundaries, and ask-first policies before destructive actions.
  • Session continuity & caching: Support warm starts, incremental discovery, and a discovery cache to speed repeated sessions and reduce redundant checks.
  • Workspace safety: Enforce filesystem/network/system limits, recommend safe tool usage, and delete transient gate flags at session start.
  • Use case: Prepare an AI agent for an isolated task run by validating the environment, loading prior session state, and producing a discovery report for downstream tasks.

Quick Start

Prepare a pre-start context discovery that reads governance.md, loads the discovery cache, checks runtimes and workspace members, and returns a summarized report of runtimes, key files, and recommended next steps.

Frequently Asked Questions about pre-start-context

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

FAQPage Schema
How do I discover project context in a monorepo before starting an AI agent task?

Discovering project context in a monorepo involves reading filesystem configurations, recent commits, and governance.md to detect runtimes, CI, and architecture patterns. This prepares the AI agent with accurate environmental state and safety guards before task execution.

What is session continuity and how does a discovery cache speed up repeated AI workflows?

Session continuity uses a discovery cache to store repository state and architecture patterns from previous runs. This enables warm starts and incremental discovery, reducing redundant filesystem checks and significantly speeding up repeated AI workflow sessions.

How do I enforce sandbox boundaries and governance rules before running destructive tasks?

Enforcing sandbox boundaries involves reading .claude/governance.md at session start to apply project-specific rules and ask-first policies. The system enforces filesystem and network limits, validating the environment before allowing destructive actions.

Does pre-task context discovery work for both single-package repos and multi-repo layouts?

Pre-task context discovery works for both single-package repos and monorepos by performing filesystem-limited discovery. It detects key config files, workspace members, and architecture patterns across various repository layouts to prepare the session.

What's the best way to load cross-session memory for an isolated AI agent run?

Loading cross-session memory requires reading an incremental discovery cache and recent repository commits. This process retrieves prior session state and environmental context, ensuring the isolated agent run starts with accurate project architecture and state.