chore: import fantasia prompts and workflows - #283
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Critical workflow loading and multiple workflow, reporting, and prompt inconsistencies remain unresolved.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (18)
Use workflow.yaml or update the workflow loader · New Prevent direct milestone comments and use report-only behavior · New Remove first-run review wait to prevent workflow deadlock · New Use a Conventional Commits-compliant PR title · New Prevent duplicate Linear comments from investigators · New Restore the merge-stage heading and objective · New Remove fallback that bypasses the mix lc repository proxy · New Rename unsupported effort settings to reasoning_effort · New Block non-reproducible issues from entering diagnosis · New Rename unsupported effort settings to reasoning_effort · New Rename unsupported effort settings to reasoning_effort · New Rename unsupported effort settings to reasoning_effort · New Chain hook commands and propagate setup failures · New Propagate git rebase and fetch failures from the hook · New Combine detached continuation into a complete instruction · New Fix typo: use “superseded” · New Complete rework instruction for recording finding outcomes · New Correct the workflow directory path in the header · New
What changed in this PR
Imports Fantasia/Stokowski workflow configuration, agent prompts, and Linear CLI guidance.
Changes:
- Adds feature, bug-fix, spike, and exploration workflows.
- Adds prompts for investigation, implementation, review, reporting, and follow-ups.
- Updates shared runtime and Linear CLI instructions.
| File | Description |
|---|---|
workflow.glean.yaml |
Shared runtime, routing, hooks, and concurrency configuration |
.ai/workflows/spike.yaml |
Spike workflow |
.ai/workflows/feature.yaml |
Feature workflow |
.ai/workflows/exploration.yaml |
Exploration workflow |
.ai/workflows/bug-fix.yaml |
Bug-fix workflow |
.ai/skills/linear/SKILL.md |
Linear CLI guidance |
.ai/prompts/review.md |
Review-stage instructions |
.ai/prompts/reproduce.md |
Bug reproduction instructions |
.ai/prompts/merge.md |
Merge-stage instructions |
.ai/prompts/investigate.md |
Investigation-stage instructions |
.ai/prompts/improvement.md |
Follow-up issue creation |
.ai/prompts/implement.md |
Implementation instructions |
.ai/prompts/ground_check.md |
Grounding verification |
.ai/prompts/global.md |
Shared agent instructions |
.ai/prompts/glean.md |
Follow-up harvesting |
.ai/prompts/explore.md |
Exploration-stage instructions |
.ai/prompts/diagnose.md |
Bug diagnosis instructions |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| @@ -0,0 +1,66 @@ | |||
| # Shared Stokowski runtime configuration. Pipelines live in workflows/*.yaml. | |||
Comment on lines
+150
to
+155
| For instance, to Post a new Linear comment (for milestone of your work, | ||
| investigation findings, implementation decisions, results, | ||
| guidance for the next stage, and so on. Do not try to maintain or | ||
| find a single running comment to update: | ||
|
|
||
| mix lc issue comment <ISSUE_ID> --body-file <path> | ||
| mise exec -- mix lc issue comment <ISSUE_ID> --body-file <path> |
Comment on lines
+35
to
+38
| 7. Review your own diff, and wait for the github review action to complete. | ||
| Once the review is posted, investigate any issues and address them | ||
| before continuing. Comment on the PR with which were actioned, which | ||
| were not, and why. |
| ``` | ||
| git push -u origin HEAD | ||
| gh pr create --title "<type>(scope): <concise title>" --body "<description>" | ||
| gh pr create --title "{{ issue.identifier }}: <concise title>" --body "<description>" |
| the human at the gate reads first, so they must carry the recommendation on | ||
| their own — someone who reads nothing else should know what to do and why. | ||
| Stokowski posts this to Linear for you. | ||
| 7. Post the summary as a Linear comment titled `## Investigation`. |
Comment on lines
+29
to
+30
| git fetch origin main | ||
| git rebase origin/main 2>/dev/null || git rebase --abort |
Comment on lines
18
to
+19
| 2. Never use interactive commands, slash commands, or plan mode. | ||
| 3. Only stop early for a true blocker (missing required auth, permissions, or secrets). | ||
| If blocked, post the blocker details as a Linear comment and stop. | ||
| 4. Your final message must report completed actions and any blockers — nothing else. | ||
| that asks the user to confirm or choose. |
|
|
||
| This project keeps its documentation in the documents/ tree. Search here | ||
| for questions about project conventions. This documentation must be | ||
| updated or appended to (plans should be superceded, not rewritten after |
Comment on lines
+59
to
60
| 4. Write a fresh `.stokowski/report.json` with the revised findings, and note | ||
|
|
| @@ -0,0 +1,66 @@ | |||
| # Shared Stokowski runtime configuration. Pipelines live in workflows/*.yaml. | |||
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
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.



No description provided.