What problem does it solve?
Autonomous repo agents that run LLMs in CI can leak write credentials, execute arbitrary commands, or push unvalidated changes. This Skill provides security standards, a workflow blueprint, and a review checklist for building repo-owned agents that run unattended without granting the model broad write access.
Core Features & Use Cases
- Two-Phase Architecture: Separates a read-only LLM audit job that produces a validated patch artifact from a publish job that owns GitHub writes and never invokes the LLM.
- Security Standards: Enforces credential isolation, scoped tool allowlists, anchored path allowlists, staged-blob validation, and prompt-injection threat modeling.
- Review Checklist: Provides merge-blocking criteria covering credentials, tools, diff validation, publish boundaries, and self-improvement constraints.
- Use Case: When building a scheduled pricing-maintenance agent that fetches provider pages and opens PRs, use this Skill to design the workflow so the LLM step has no write token, no shell access, and every changed file passes independent diff validation before a bot publishes the PR.
Quick Start
Use the create-repo-agent skill to design a scheduled GitHub Actions agent that audits a config file and opens a validated PR without giving the LLM write credentials.