Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[P1] Auto-create Gitea issues from research findings #977

New Issue
Closed
opened 2026-03-22 19:08:53 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-22 19:08:53 +00:00
Collaborator
Copy Link

Parent

  • #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec

Objective

Implement extract_action_items(report) and create_gitea_issue(issue) functions so the research orchestrator automatically triages findings into the engineering backlog.

Scope

  • Parse structured research output for action items, recommendations, and work suggestions
  • Create Gitea issues via API with appropriate labels (actionable, kimi-ready, etc.)
  • Link child issues back to the research source issue
  • Include source URLs and evidence in issue bodies

Key Design Notes

  • This closes the loop: research → knowledge → actionable work
  • Gitea API is already used throughout the project
  • Action items should be extracted by the LLM during synthesis, not post-processed

Effort Estimate

4 hours

Related

  • #911 — Wire Gitea API for PR creation (similar API usage pattern)
## Parent - #972 — [GOVERNING] Replacing Claude — Autonomous Research Pipeline Spec ## Objective Implement `extract_action_items(report)` and `create_gitea_issue(issue)` functions so the research orchestrator automatically triages findings into the engineering backlog. ## Scope - Parse structured research output for action items, recommendations, and work suggestions - Create Gitea issues via API with appropriate labels (`actionable`, `kimi-ready`, etc.) - Link child issues back to the research source issue - Include source URLs and evidence in issue bodies ## Key Design Notes - This closes the loop: research → knowledge → actionable work - Gitea API is already used throughout the project - Action items should be extracted by the LLM during synthesis, not post-processed ## Effort Estimate 4 hours ## Related - #911 — Wire Gitea API for PR creation (similar API usage pattern)
claude self-assigned this 2026-03-22 23:37:29 +00:00
claude commented 2026-03-23 02:15:36 +00:00
Collaborator
Copy Link

PR #1060 created.

Implemented extract_action_items(), create_gitea_issue(), and triage_research_report() in src/timmy/research_triage.py. The module uses the LLM to extract 0-5 concrete action items from research reports, then files them as Gitea issues with labels (actionable, kimi-ready, etc.), source evidence URLs, and links back to the parent research issue. 28 unit tests cover all paths including graceful degradation.

PR #1060 created. Implemented `extract_action_items()`, `create_gitea_issue()`, and `triage_research_report()` in `src/timmy/research_triage.py`. The module uses the LLM to extract 0-5 concrete action items from research reports, then files them as Gitea issues with labels (actionable, kimi-ready, etc.), source evidence URLs, and links back to the parent research issue. 28 unit tests cover all paths including graceful degradation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#977
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?