chore: improve agent harness skills (#1378)

2026-06-15 22:45:48 +01:00
parent 0bc91a62b3
commit 19c17b1321
67 changed files with 2413 additions and 680 deletions
@@ -0,0 +1,13 @@
+---
+description: Update Kandev harness files from session learnings or explicit cross-platform harness requests.
+argument-hint: "[learning or requested harness change]"
+allowed-tools: Bash Read Edit Write Grep Glob
+model: inherit
+effort: medium
+---
+
+Use `.agents/skills/harness-improvement/SKILL.md`.
+
+First read the relevant bundled reference files under `.agents/skills/harness-improvement/references/`. For platform-specific formats, use `references/platforms/` as the first source of truth and do not browse unless a bundled reference is missing, contradictory, or the user explicitly asks for latest upstream behavior.
+
+Honor the user's scope. For subagents, update all requested project-local platform mirrors. Do not commit unless explicitly asked.
@@ -0,0 +1,13 @@
+---
+description: Run the Kandev PR fixup loop for CI failures and automated review threads.
+argument-hint: "<PR number>"
+allowed-tools: Bash Read Edit Write Grep Glob
+model: sonnet
+effort: high
+---
+
+Use `.agents/skills/pr-fixup/SKILL.md`.
+
+Resolve the PR number, use `scripts/pr-state --summary <PR>` from the repo root for state, use `scripts/pr-resolve list <PR>` for actionable threads, and use `scripts/pr-resolve reply <PR> <comment_id> <thread_id> <body>` for replies.
+
+Fix failed checks and unresolved current-head review threads. After pushing fixes, re-check with `scripts/pr-state --summary <PR>`; if there are no failed checks and no unresolved review threads but checks remain pending, report the exact pending state instead of waiting indefinitely unless the user asked to wait.
@@ -0,0 +1,17 @@
+---
+description: Drive Kandev feature work through spec, plan, independent tasks, implementation, QA, and verification.
+argument-hint: "[feature or fix goal]"
+allowed-tools: Bash Read Edit Write Grep Glob
+model: inherit
+effort: high
+---
+
+Use Kandev's spec-driven flow:
+
+1. Clarify intent with `/interview-me` style questions when needed.
+2. Create or update the product spec with `/spec`.
+3. Create the implementation plan with `/plan`.
+4. Decompose into independent tasks with acceptance criteria, exact verification, likely files, dependencies, and wave ordering.
+5. Delegate independent work to `architect`, `implementer`, `test-engineer`, `qa`, `security-auditor`, `code-review`, `simplify`, and `verify` as appropriate.
+
+Keep the parent agent responsible for orchestration, integration order, user communication, and final status.