Loading...
Loading...
Found 43 Skills
Manage Harness Infrastructure as Code Management (IaCM) via MCP. Configure Terraform workspaces with remote state and RBAC, set up continuous drift detection with auto-remediation, design multi-tier change approval workflows, and estimate infrastructure costs before deployment. Use when asked to manage Terraform workspaces, detect infrastructure drift, set up approval workflows for infrastructure changes, or estimate Terraform costs. Do NOT use for creating Harness infrastructure definitions (use create-infrastructure instead) or OPA policies (use create-policy instead). Trigger phrases: terraform, workspace, drift detection, infrastructure cost, IaCM, state management, change approval, terraform plan, infracost, infrastructure governance.
Enforce allowed and forbidden conversation topics using semantic embedding similarity with session-aware drift detection
Comprehensive content review and quality assurance for BRD documents - validates link integrity, requirement completeness, strategic alignment, and identifies issues requiring manual attention
Runs drift detection on all design documents to check for document and code consistency. Produces an actionable report with differences. Use when the user asks to detect drift or check for consistency across all design documents or READMEs in a directory.
Reconcile the code graph in memory (wiki substrate) against the actual codebase. In --touched mode, re-summarizes only files a completed plan touched (cheap, post-plan gate). In --sweep mode, walks the whole repo and patches drift from out-of-band edits. Drift is accepted between gates; this skill is the only place the code graph is reconciled to the repo tree.
Set up and run Git-backed schema sync between a repository and Prepr CMS environments, with schema files in prepr/schema/. Use this skill whenever the user wants to sync a Prepr schema via GitHub, GitLab, Bitbucket or Azure DevOps, get local schema file changes into a Prepr environment, export an environment's schema to the repository, promote schema between development, acceptance and production, add schema validation to CI, debug a schema import that fails or returns github.validation.failed, check whether the schema files and an environment have drifted, or asks why schema file edits have not appeared in Prepr. Also use it when the user considers direct environment-to-environment sync.
Kiểm tra sức khỏe "pattern chuẩn" của template — pattern đã đủ chưa, có drift local không, và có cần /sync-template từ remote không. So version.json local ↔ remote ↔ disk (0 token, fail- open). Trigger: "health check", "check pattern", "cần sync chưa", "/health-check".