chore(cursor): enum-shared-type-migration automation and ai-agents alignment#994
Merged
georgewrmarshall merged 15 commits intomainfrom Apr 7, 2026
Merged
Conversation
- Add component-migration-project.md with project overview and status - Add extension-migration-tracker.md with Extension component status - Add mobile-migration-tracker.md with Mobile component status - Add jira-ticket-creation.md with ticket creation workflows - Add component-migration-tracking.md cursor rule for tracking workflow
Made-with: Cursor
- Add canonical steps and PR/GitHub auth notes in automations doc - Point rule at automations file for @-mention workflow Made-with: Cursor
Made-with: Cursor
… docs Made-with: Cursor
…d cloud prompt Made-with: Cursor
…s, verification) Made-with: Cursor
Made-with: Cursor
Contributor
📖 Storybook Preview |
Made-with: Cursor
Contributor
📖 Storybook Preview |
- Drop component-migration-tracking rule and standalone tracker docs - Remove enum-shared-type-migration.mdc; invoke automation via .cursor/automations only - Fix ai-agents and automation doc references Made-with: Cursor
Contributor
📖 Storybook Preview |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Hardcoded user-specific assignee in shared board URL
- Removed the hardcoded assignee parameter from the Jira board URL so it reflects the full epic scope.
Or push these changes by commenting:
@cursor push b7ee51b32c
Preview (b7ee51b32c)
diff --git a/.cursor/automations/enum-shared-type-migration.md b/.cursor/automations/enum-shared-type-migration.md
--- a/.cursor/automations/enum-shared-type-migration.md
+++ b/.cursor/automations/enum-shared-type-migration.md
@@ -18,7 +18,7 @@
| Setting | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Epic | **DSYS-468** — _Component ADR Migration: Align with ADR-0003 and ADR-0004_ |
-| Board (reference) | [DSYS board — epic filter](https://consensyssoftware.atlassian.net/jira/software/c/projects/DSYS/boards/1888?assignee=6152e94cc7bea40069d6b9c3&issueParent=343549) |
+| Board (reference) | [DSYS board — epic filter](https://consensyssoftware.atlassian.net/jira/software/c/projects/DSYS/boards/1888?issueParent=343549) |
## 1. Find candidatesYou can send follow-ups to this agent here.
Contributor
📖 Storybook Preview |
Contributor
Author
…how full epic scope Applied via @cursor push command
Contributor
📖 Storybook Preview |
Contributor
📖 Storybook Preview |
brianacnguyen
approved these changes
Apr 7, 2026
Contributor
📖 Storybook Preview |
georgewrmarshall
deleted the
chore/cursor-enum-shared-type-migration-automation
branch
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
3 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.
Description
Why
Cursor Automations are configured in the Cursor product UI and are not version-controlled in git. We need an in-repo canonical spec for the DSYS-468 / ADR-0003–0004 internal migration workflow (Jira pickup, which rules to follow, verification, PR expectations) so it can be reviewed in PRs and linked or copy-pasted into Private or Team Visible automations.
What changed
.cursor/automations/enum-shared-type-migration.md— JQL (interactive vs scheduled unassigned backlog), Jira pickup steps, Cursor Cloud Automation notes (billing/identity, tools), implementation pointers toCLAUDE.mdand Layer 2 rules (component-enum-union-migration, etc.), verification (yarn build,yarn test,yarn lint), and a paste-ready cloud prompt.docs/ai-agents.md— Cursor Cloud Automations subsection aligned with repo agent principles (reference over duplication, checklists, context efficiency, verification) and explicit note that.cursor/automations/is the VCS source of truth because the Automations UI has no native version control..cursor/rules/component-migration-tracking.md,.cursor/rules/enum-shared-type-migration.mdc, and docscomponent-migration-project.md,extension-migration-tracker.md,jira-ticket-creation.md,mobile-migration-tracker.md. Automation is invoked via@.cursor/automations/enum-shared-type-migration.mdonly (no companion.mdcrule).Linking specs from Cursor Automations (for reviewers)
There is no official Cursor documentation that guarantees a cloud agent will fetch and follow an arbitrary GitHub blob URL. Recommended: configure the automation with a repository + branch that contains this file, and instruct the agent to read
.cursor/automations/enum-shared-type-migration.mdin the workspace. A GitHub link (especiallyraw.githubusercontent.comor a pinned commit) is still useful for humans, pinning a frozen spec, or external tooling—but treat it as supplementary to the checked-out file.Related issues
Fixes: (none — contributor workflow / tooling only)
Manual testing steps
.cursor/automations/enum-shared-type-migration.mdand confirm structure, JQL blocks, and links render as expected.@-mention.cursor/automations/enum-shared-type-migration.mdand confirm the agent is directed todocs/ai-agents.mdand the listed@.cursor/rules/*.mdfiles for implementation (notcomponent-migration.mdfor this epic).component-migration-tracking, removed tracker docs) via repo search..cursor/automations/enum-shared-type-migration.mdon disk.Example PRs
PRs that have been successfully created with this automation
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Low risk: documentation-only changes that do not affect runtime code paths. Primary risk is process confusion if the new automation guidance is followed incorrectly.
Overview
Adds
.cursor/automations/enum-shared-type-migration.mdas the canonical, in-repo spec for the DSYS-468 enum→union/shared-type migration workflow, including Jira JQL pickup/claim steps, required rule references (@CLAUDE.md,@.cursor/rules/*), verification commands, PR expectations, and paste-ready prompts (including a post-merge Jira-close flow).Updates
docs/ai-agents.mdto explicitly document Cursor Cloud Automations best practices and to establish.cursor/automations/as the version-controlled source of truth since the Cursor UI prompt is not tracked.Reviewed by Cursor Bugbot for commit 422ac8c. Bugbot is set up for automated code reviews on this repo. Configure here.