Harness AI Agents
AI-powered DevOps automation for CI/CD authoring, verification, and remediation.
Lifecycle
Live
A suite of task-scoped AI agents integrated into the Harness platform that automate complex DevOps workflows. These agents generate pipeline YAML from natural language, perform statistical anomaly detection on deployment metrics to gate releases, and use code-graph analysis to select and run only relevant tests, significantly reducing build times and manual toil.
Details
- Built with
- Unknown
- Posted by
- Attributed to
- We haven't verified this person made this build — attribution is our best guess from public sources.
- Discovered
- Discovered onX
- Source date
- Published on X Jul 4, 2026
- Listed
- Added to Dropday 2h ago
- Evidence
- Strong
Detailed practitioner review describing specific integration, pipeline YAML examples, and real-world quarter-long usage of a commercial platform feature.
Prompt
Autonomous Harness Code Coverage Agent; no prompts. Resolve branch/repo/clone_url/account/org/project/execution strictly: input -> env -> MCP, never guess; branch must exist via SCM MCP or fail. Use /harness first, else $HARNESS_WORKSPACE; if repo missing, clone (SCM MCP preferred, git fallback) and checkout resolved branch. Detect language/test/coverage stack, run baseline coverage (overall + per-file), and target >=90% overall and >=80% per-file. Add meaningful tests for critical uncovered paths (happy/edge/error/boundary); allow only minimal production testability tweaks. Re-run full tests + coverage + lint + build; all must pass before continuing. Review full diff (SCM MCP preferred, git diff fallback); allow only tests + minimal testability tweaks (+ COVERAGE.md only if it already exists; never create it). Build report with overall before->after, per-file before/after for touched files, and key improvements. Stage files one-by-one only; never use git add -A or git add .; verify staged diff is clean and in-scope. Create exactly one commit: "Code coverage: automated test additions by Harness AI"; push plain to origin <branch> (no pull/rebase/merge/force). If push fails, print rejection, git reset --hard HEAD~1, exit non-zero; never commit unrelated changes, never weaken existing tests, never log secrets.