intake: regenerate the dashboard in the same commit as the filed prompt - #286
Merged
Jammy2211 merged 1 commit intoAug 25, 2026
Merged
Conversation
…d prompt Same gap /prm had, at the other end of the lifecycle. `intake --apply` writes the prompt file and runs no git at all, and the skill treated the render as optional — "regenerate it by hand only when you want the page current in the same commit" — leaving it to dashboard_refresh.yml. But filing a prompt is a dashboard-changing act, and the dashboard is the pickup mechanism: tap 📋, get `/start_dev <path>`. A prompt filed without the regen is invisible on that path until the workflow heals the render AND re-dispatches pages_dashboard.yml, because its heal commit is made with GITHUB_TOKEN and triggers no other workflow. Filing a task nobody can find yet is the failure this closes. - Do gains step 4: regenerate, `--check`, and `prompt_sync_push` the prompt and both pages as one commit. Called out as covering `formalise` and the `ideas` sweep too, which change the page the same way. - The "self-heals, so regenerate by hand only when…" line now says what that backstop actually is: cover for a page nobody rebuilt, and later to Pages than a correctly-committed render. - SKILL.md states that --apply runs no git, so filing is not finished until the page is committed with it. Re-rendering an already-current tree is a no-op (verified while doing the /prm change), so there is no judgement call here — it runs on every --apply. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011QFJaycmUfaEhR4XoZajy9
github-actions
Bot
deleted the
claude/automind-dashboard-incomplete-tasks-8d9h20
branch
August 26, 2026 20:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The same gap #285 closed for
/prm, at the other end of the lifecycle.intake --applywrites the prompt file and runs no git at all — the onlysubprocessgit call in_intake.pyis inside thereconcile --reporeader. The skill then treated the render as optional: "regenerate it by hand only when you want the page current in the same commit."But filing a prompt is a dashboard-changing act, and the dashboard is the pickup mechanism — tap the 📋, get
/start_dev <path>. A prompt filed without the regen is invisible on that path untildashboard_refresh.ymlheals the render and re-dispatchespages_dashboard.yml, which it must do explicitly because its heal commit is made withGITHUB_TOKENand triggers no other workflow. Filing a task nobody can find yet is the failure this closes.What changes
Dogains step 4 — regenerate,--check, andprompt_sync_pushthe prompt and both pages as a single commit. Stated to coverformaliseand theideassweep as well, since they change the page the same way.SKILL.mdstates that--applyruns no git, so filing is not finished until the page is committed with it.Re-rendering an already-current tree is a no-op — both files are rewritten byte-identically and
git statusstays clean (verified while doing #285). So there is no judgement call about whether it is needed; it runs on every--apply.Scope
Documentation only, two files in
skills/intake/. No agent or script behaviour changes.install.sh --check-agents-surfaceclean.Generated by Claude Code