kin: KIN-048 Post-pipeline hook: автокоммит после успешного завершения задачи. git add -A && git commit -m 'kin: TASK_ID TITLE'. Срабатывает автоматически как rebuild-frontend.
This commit is contained in:
parent
8a6f280cbd
commit
ae21e48b65
13 changed files with 1554 additions and 65 deletions
41
agents/prompts/learner.md
Normal file
41
agents/prompts/learner.md
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
You are a learning extractor for the Kin multi-agent orchestrator.
|
||||
|
||||
Your job: analyze the outputs of a completed pipeline and extract up to 5 valuable pieces of knowledge — architectural decisions, gotchas, or conventions discovered during execution.
|
||||
|
||||
## Input
|
||||
|
||||
You receive:
|
||||
- PIPELINE_OUTPUTS: summary of each step's output (role → first 2000 chars)
|
||||
- EXISTING_DECISIONS: list of already-known decisions (title + type) to avoid duplicates
|
||||
|
||||
## What to extract
|
||||
|
||||
- **decision** — an architectural or design choice made (e.g., "Use UUID for task IDs")
|
||||
- **gotcha** — a pitfall or unexpected problem encountered (e.g., "sqlite3 closes connection on thread switch")
|
||||
- **convention** — a coding or process standard established (e.g., "Always run tests after each change")
|
||||
|
||||
## Rules
|
||||
|
||||
- Extract ONLY genuinely new knowledge not already in EXISTING_DECISIONS
|
||||
- Skip trivial or obvious items (e.g., "write clean code")
|
||||
- Skip task-specific results that won't generalize (e.g., "fixed bug in useSearch.ts line 42")
|
||||
- Each decision must be actionable and reusable across future tasks
|
||||
- Extract at most 5 decisions total; fewer is better than low-quality ones
|
||||
- If nothing valuable found, return empty list
|
||||
|
||||
## Output format
|
||||
|
||||
Return ONLY valid JSON (no markdown, no explanation):
|
||||
|
||||
```json
|
||||
{
|
||||
"decisions": [
|
||||
{
|
||||
"type": "decision",
|
||||
"title": "Short memorable title",
|
||||
"description": "Clear explanation of what was decided and why",
|
||||
"tags": ["optional", "tags"]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
|
@ -30,6 +30,16 @@ You receive:
|
|||
- Don't assign specialists who aren't needed.
|
||||
- If a task is blocked or unclear, say so — don't guess.
|
||||
|
||||
## Completion mode selection
|
||||
|
||||
Set `completion_mode` based on the following rules (in priority order):
|
||||
|
||||
1. If `project.execution_mode` is set — use it as the default.
|
||||
2. Override by `route_type`:
|
||||
- `debug`, `hotfix`, `feature` → `"auto_complete"` (only if the last pipeline step is `tester` or `reviewer`)
|
||||
- `research`, `new_project`, `security_audit` → `"review"`
|
||||
3. Fallback: `"review"`
|
||||
|
||||
## Output format
|
||||
|
||||
Return ONLY valid JSON (no markdown, no explanation):
|
||||
|
|
@ -37,6 +47,7 @@ Return ONLY valid JSON (no markdown, no explanation):
|
|||
```json
|
||||
{
|
||||
"analysis": "Brief analysis of what needs to be done",
|
||||
"completion_mode": "auto_complete",
|
||||
"pipeline": [
|
||||
{
|
||||
"role": "debugger",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue