submodule-lazy-provisioning Skill
Manifest-driven git submodule pattern for large, optional locally-run apps: register the gitlink at a pinned SHA, defer the actual clone to a lazy helper script, expose via npm script, and drift-check on every CI run. Published by microsoft in frontier-agentic-devops-rvas.
Decision snapshot
Is this a fit?
Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is submodule-lazy-provisioning Skill?
Manifest-driven git submodule pattern for large, optional locally-run apps: register the gitlink at a pinned SHA, defer the actual clone to a lazy helper script, expose via npm script, and drift-check on every CI run. Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Writing
- Writing use cases
Declared skill metadata
- Source file: .squad/skills/submodule-lazy-provisioning/SKILL.md
Compatibility and setup
- Install or run with Copy skill directory
When to use submodule-lazy-provisioning Skill
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/skills/submodule-lazy-provisioning/SKILL.md
What it does
Manifest-driven git submodule pattern for large, optional locally-run apps: register the gitlink at a pinned SHA, defer the actual clone to a lazy helper script, expose via npm script, and drift-check on every CI run.
Skill instructions
Context Use when a curriculum or tooling repo needs to pin a large external app at a specific commit for local participant use, but: - The app is too large to vendor in-tree - Most users don't need it (lazy fetch is preferred) - The exact commit must be guaranteed (drift check required) - Participants need a stable path regardless of internal submodule layout Patterns 1. Register submodule without cloning bash Create empty working-tree placeholder mkdir -p external/<name Write gitlink directly into git index at the pinned SHA (no network) git update-index --add --cacheinfo 160000,<sha,external/<name Register URL + shallow=true in .gitmodules cat .gitmodules << EOF [submodule "external/<name"] path = external/<name url = <url shallow = true EOF git add .gitmodules This produces a valid submodule registration (gitlink + URL) without any network access. The gitlink object in the parent repo's tree stores the exact SHA. 2. Committed symlink for stable paths bash ln -s external/<name app or
Verified compatibility and discovery
Frequently asked questions
What is submodule-lazy-provisioning?
submodule-lazy-provisioning is a open-source AI agent skill with Copy skill directory. Manifest-driven git submodule pattern for large, optional locally-run apps: register the gitlink at a pinned SHA, defer the actual clone to a lazy helper script, expose via npm script, and.
Who is submodule-lazy-provisioning best for?
submodule-lazy-provisioning is best for reusing agent instructions, scripts, and references, writing workflows.
How do I install submodule-lazy-provisioning?
Install or run submodule-lazy-provisioning using Copy skill directory. Check submodule-lazy-provisioning for the latest setup command.
Is submodule-lazy-provisioning actively maintained?
submodule-lazy-provisioning may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
