load-context

name	load-context
description	Internal resource bundle for rev-review, rev-audit, and rev-verify skills. Holds shared review principles, language pack detection, agent prompts, and audit focuses. Do not invoke directly — the rev-* skills read its resources via `../load-context/resources/` paths.
disable-model-invocation	true

! ls package.json tsconfig.json jsconfig.json go.mod Cargo.toml pyproject.toml requirements.txt pom.xml build.gradle build.gradle.kts settings.gradle settings.gradle.kts gradlew gradlew.bat mvnw mvnw.cmd bun.lockb package-lock.json yarn.lock pnpm-lock.yaml composer.json composer.lock artisan symfony.lock phpstan.neon phpstan.neon.dist psalm.xml psalm.xml.dist phpunit.xml phpunit.xml.dist 2>/dev/null

ALWAYS READ

1. Load resources/core/principles/always.md

Language Pack Detection

Detect the project's languages from manifest files in the working directory:

Manifest Files	Language Pack	Core Patterns
package.json, tsconfig.json, jsconfig.json, bun.lockb, package-lock.json, yarn.lock, pnpm-lock.yaml	typescript	resources/languages/typescript/core-patterns.md
composer.json	php	resources/languages/php/core-patterns.md
pom.xml, build.gradle, build.gradle.kts, settings.gradle, settings.gradle.kts, gradlew, mvnw	java	resources/languages/java/core-patterns.md

For each detected language pack:

1. Load the pack's core patterns (listed above)
2. Read the pack's resources/languages/<lang>/index.md for the trigger table
3. Load framework/tool-specific resources as triggers match the project

Configuration

All shared review resources live in resources/ relative to this skill:

• Core logic: resources/core/
• Agent prompts: resources/agent/
• Language packs: resources/languages/

The review prompt directory is: resources/

Capabilities

PR / Commit Review

When asked to review a PR, commit, or set of changes:

1. Load resources/core/review-core.md
2. Follow the complete review protocol defined there
3. Load language pack resources as directed by review-core.md
4. Use Context7 CLI for documentation validation

Project Audit

When asked to audit a project:

1. Load resources/core/audit-core.md
2. Follow the complete audit protocol defined there
3. Activate situational focuses based on user instructions

Language Pack Context

When working on code in specific frameworks, load the appropriate context files:

1. Always read the core principles and pack core patterns first
2. Read the pack's resources/languages/<lang>/index.md and load matching resources based on imports and file paths in the current context

Context7 CLI Integration

When available, use Context7 CLI for documentation validation:

• ctx7 library: Resolve framework library IDs
• ctx7 docs: Fetch current documentation for specific APIs

Always validate framework API usage against current docs when:

• New framework APIs are introduced in the change
• Unusual patterns are detected
• Version-specific behavior is suspected

Non-Dogmatic Approach

If a conflict is detected between review resources and Context7 documentation, or something seems incoherent, ask the user rather than assuming either source is correct.

Output

• PR reviews produce review.md and review-metadata.json
• Project audits produce audit-report.md and audit-metadata.json
• Both outputs are formatted as markdown with structured JSON metadata