coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
activity-core/activity-definitions/weekly-coding-retro.md
tegwick 4f5399df84
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details
Build and Publish Container Image / build-and-push (push) Successful in 28s
Details
Implement ACTIVITY-WP-0022/0023: safe sink default and gap closures 
Default ISSUE_SINK_TYPE to state-hub (no silent Forgejo issues), hard-fail
prune apply without live-images protection, refresh-live-images script,
disable TaskExecutor stub by default, and document consumer/sink contracts.
2026-07-21 21:40:08 +02:00

1.5 KiB
Raw Blame History

id name enabled owner governance status trigger context_sources
weekly-coding-retro Weekly Coding Retrospection false custodian-agent custodian proposed
type cron_expression timezone misfire_policy
cron 0 19 * * 6 Europe/Berlin skip
type query params bind_to
state-hub coding_retro
window_days limit
7 100
context.retro

Weekly Coding Retrospection

Runs every Saturday 19:00 Berlin time. Reads the previous week's coding-session analysis (published to the hub by helix_forge session-memory) and opens one improvement suggestion per relevant repo — the three most promising, already ranked upstream.

id: propose-weekly-improvements
for_each: context.retro.suggestions
bind_as: s
condition: 'context.s.score > 0'
action:
  task_template: context.s.title
  description: context.s.recommendation
  target_repo: context.s.repo
  priority: context.s.priority
  labels: ["coding-retro", "improvement", "automated"]

Each suggestion carries repo, title, recommendation, priority, and score. The upstream retro caps the list at three per repo, so this emits at most three improvement tasks per relevant repository per week.