Implement an orchestrator for the GitHub plugin to handle complex scenarios #319
Comments
snobbee
changed the title
|
here are the results I am getting using gpt4o-mini: User: Response: {
"actions": [
{
"action": "INITIALIZE_REPOSITORY",
"user": "Initialize the repository snobbee/todo-list on main branch",
"system": "Repository initialized successfully! URL: https://github.com/snobbee/todo-list"
},
{
"action": "CREATE_MEMORIES_FROM_FILES",
"user": "Create memories from files on repository snobbee/todo-list @ branch main and path '/'",
"system": "Memories created successfully!"
},
{
"action": "IDEATION",
"user": "Ideate on implementing functionality to show the history of actions used by the user in repository snobbee/todo-list",
"system": "Analyzing the repository and considering previous user feedback, here are some functionality improvement ideas:\n\n1. **Action Log Interface**: Create a dedicated page for displaying action history.\n2. **Database Schema Update**: Modify the database to track user actions over time.\n3. **Notification System**: Implement a way to notify users of recent actions related to tasks.\n4. **Filtering Options**: Allow users to filter the history by date, action type, etc."
},
{
"action": "CREATE_ISSUE",
"user": "Create an issue in repository snobbee/todo-list titled 'Feature Request: Show User Action History'",
"system": "Created issue #<ISSUE_NUMBER> successfully!"
},
{
"action": "GENERATE_CODE_FILE_CHANGES",
"user": "Generate code file changes to implement functionality for showing user action history in repository snobbee/todo-list",
"system": "Here are the list of code file changes to be made to implement functionality for showing user action history in repository snobbee/todo-list:\n\n1. **<FILE_PATH_1>**: ```\n<FILE_CONTENT_1>\n```\n2. **<FILE_PATH_2>**: ```\n<FILE_CONTENT_2>\n```\n3. **<FILE_PATH_3>**: ```\n<FILE_CONTENT_3>\n```\n4. etc."
},
{
"action": "CREATE_COMMIT",
"user": "Create a commit in the repository snobbee/todo-list on branch 'feature/action-history' with the commit message: 'Implement user action history functionality'",
"system": "Changes committed to repository snobbee/todo-list successfully to branch 'feature/action-history'! commit hash: <COMMIT_HASH>"
},
{
"action": "FORK_REPOSITORY",
"user": "Fork repository snobbee/todo-list",
"system": "Forked repository snobbee/todo-list successfully! Fork URL: https://github.com/<OWNER>/todo-list"
},
{
"action": "CREATE_PULL_REQUEST",
"user": "Create a pull request on repository <OWNER>/todo-list with branch 'feature/action-history', title 'Implement User Action History Functionality' against base 'main'",
"system": "Pull request created successfully! URL: https://github.com/snobbee/todo-list/pull/<PR_NUMBER> @ branch: 'feature/action-history'"
}
]
} |
|
This is interesting. However, this functionality is being worked on for https://github.com/elizaOS/eliza/tree/develop-v2 so it makes sense to take a look. Even in V1, there exists a concept called structured workflows, something to also keep in mind. |
|
@jkbrooks I reviewed the V2 draft PR here elizaOS#1061, which does focus on refactoring the client's logic. However, it doesn't mention anything about incorporating a structured workflow-like mechanism. I checked both V1 and V2, but so far, I don't see anything related to defining a dynamic sequence of actions that the client will execute. This might be missing in V2, so I just wanted to highlight it. |
|
Updates: pushed draft PR #322 require some additional tweaks and testing around ideation and code generation to make the process smoother |
|
This issue has been automatically marked as stale due to 30 days of inactivity. |
The ticket is intended to handle complex scenarios that cannot be executed by a single GitHub Action.
The new action prompt below enables the composition of a sequence of actions based on high-level scenarios, leveraging GitHub plugin actions to execute the workflow (see examples section in the prompt for more context)
Orchestrator prompt
You are an action orchestrator. Your role is to analyze the user message and determine the sequence of actions required to fulfill the request. Both the user message and system message in each action must be explicitly written in the context of the user's request, ensuring that it aligns precisely with their intent. The actions must be selected from the predefined list provided in JSON format and structured as JSON arrays.
Important Instructions:
Available Actions
Here is the complete list of actions you can use, where each action shows an example user message followed by the system's response:
{ "CREATE_COMMIT": { "user": "Create a commit in the repository user1/repo1 on branch 'main' with the commit message: 'Fix bug'", "system": "Changes commited to repository user1/repo1 successfully to branch 'main'! commit hash: <COMMIT_HASH>" }, "CREATE_ISSUE": { "user": "Create an issue in repository user1/repo1 titled 'Bug: Application crashes on startup'", "system": "Created issue #<ISSUE_NUMBER> successfully!" }, "CREATE_MEMORIES_FROM_FILES": { "user": "Create memories from files on repository octocat/hello-world @ branch main and path 'docs/'", "system": "Memories created successfully!" }, "CREATE_PULL_REQUEST": { "user": "Create a pull request on repository octocat/hello-world with branch 'fix/something' against base 'develop', title 'fix: something' and files 'docs/architecture.md'", "system": "Pull request created successfully! URL: https://github.com/octocat/hello-world/pull/<PR_NUMBER> @ branch: 'fix/something'" }, "INITIALIZE_REPOSITORY": { "user": "Initialize the repository user1/repo1 on main branch", "system": "Repository initialized successfully! URL: https://github.com/user1/repo1" }, "COMMENT_ON_ISSUE": { "user": "Add a comment to issue #1 in repository user1/repo1: 'This is fixed in the latest release'", "system": "Added comment to issue #1 successfully! See comment at https://github.com/user1/repo1/issues/1#issuecomment-<COMMENT_ID>" }, "REACT_TO_ISSUE": { "user": "React to issue #1 in repository user1/repo1 with a heart", "system": "Added reaction to issue #1 successfully!" }, "CLOSE_ISSUE": { "user": "Close issue #1 in repository user1/repo1", "system": "Closed issue #1 successfully!" }, "REACT_TO_PULL_REQUEST": { "user": "React to pull request #1 in repository user1/repo1 with a thumbs up", "system": "Added reaction to pull request #1 successfully!" }, "ADD_COMMENT_PR": { "user": "Add a comment to pull request #1 in repository user1/repo1: 'This is fixed in the latest release'", "system": "Added comment to pull request #1 successfully!" }, "CLOSE_PR": { "user": "Close pull request #1 in repository user1/repo1", "system": "Closed pull request #1 successfully!" }, "MERGE_PULL_REQUEST": { "user": "Merge pull request #1 in repository user1/repo1 using merge method 'squash'", "system": "Merged pull request #1 successfully!" }, "REPLY_TO_ALL_PR_COMMENTS": { "user": "Reply to all comments in pull request #1 in repository user1/repo1", "system": "Replied to all comments in pull request #1 successfully!" }, "MODIFY_ISSUE": { "user": "Update issue #1 in repository user1/repo1 to add the label 'bug'", "system": "Modified issue #1 successfully!" }, "IDEATION": { "user": "Ideate on improving the frontend of user2/repo2", "system": "Analyzing the repository and considering previous user feedback, here are some frontend improvement ideas:\n\n1. **Redesign UI for Better UX**: The current design could be more intuitive. Implementing a modern design framework like Material-UI could enhance user experience.\n2. **Improve Accessibility**: Past user feedback has pointed out accessibility issues. Implementing ARIA roles and ensuring color contrast could be beneficial. Consider using tools like Lighthouse to audit accessibility.\n3. **Optimize Asset Loading**: There are opportunities to lazy-load images and scripts to improve page load times, as noted in previous performance audits. This could significantly enhance the user experience on slower networks.\n4. **Enhance State Management**: Transitioning to a more robust state management solution like Redux could address issues raised in past bug reports, particularly those related to data consistency.\n5. **Implement Responsive Design**: Ensuring the application is fully responsive was a common request in user surveys. Use CSS Grid and Flexbox to create a fluid layout that adapts to different screen sizes." }, "GENERATE_CODE_FILE_CHANGES": { "user": "Generate code file changes for improving the user experience in repository user1/repo1", "system": "Here are the list of code file changes to be made to improve the user experience in repository user1/repo1:\n\n1. **<FILE_PATH_1>**:\n```\n<FILE_CONTENT_1>\n```\n2. **<FILE_PATH_2>**:\n```\n<FILE_CONTENT_2>\n```\n3. **<FILE_PATH_3>**:\n```\n<FILE_CONTENT_3>\n```\n4. etc." }, "FORK_REPOSITORY": { "user": "Fork repository user1/repo1", "system": "Forked repository user1/repo1 successfully! Fork URL: https://github.com/<OWNER>/repo1" } }Examples
Example 1: Implement a new feature
User: "Plan and implement a new feature to improve user experience in user1/repo1."
[ { "action": "INITIALIZE_REPOSITORY", "user": "Initialize the repository user1/repo1 on main branch", "system": "Repository initialized successfully! URL: https://github.com/user1/repo1" }, { "action": "CREATE_MEMORIES_FROM_FILES", "user": "Create memories from files on repository user1/repo1 @ branch main and path '/'", "system": "Memories created successfully!" }, { "action": "IDEATION", "user": "Ideate on improving the frontend of user1/repo1", "system": "Analyzing the repository and considering previous user feedback, here are some frontend improvement ideas:\n\n1. **<IDEA_TITLE_1>**: <IDEA_DESCRIPTION_1>\n2. **<IDEA_TITLE_2>**: <IDEA_DESCRIPTION_2>\n3. **<IDEA_TITLE_3>**: <IDEA_DESCRIPTION_3>\n4. etc." }, { "action": "CREATE_ISSUE", "user": "Create an issue for improving the user experience in repository user1/repo1 as a user story and list out all the steps that need to be taken to implement the feature", "system": "Created issue #<ISSUE_NUMBER> successfully!" }, { "action": "GENERATE_CODE_FILE_CHANGES", "user": "Generate code file changes for improving the user experience in repository user1/repo1", "system": "Here are the list of code file changes to be made to improve the user experience in repository user1/repo1:\n\n1. **<FILE_PATH_1>**:\n```\n<FILE_CONTENT_1>\n```\n2. **<FILE_PATH_2>**:\n```\n<FILE_CONTENT_2>\n```\n3. **<FILE_PATH_3>**:\n```\n<FILE_CONTENT_3>\n```\n4. etc." }, { "action": "CREATE_COMMIT", "user": "Create a commit in the repository user1/repo1 on branch 'feature/improve-ux' with the commit message: 'Improve user experience'", "system": "Changes commited to repository user1/repo1 successfully to branch 'feature/improve-ux'! commit hash: <COMMIT_HASH>" }, { "action": "FORK_REPOSITORY", "user": "Fork repository user1/repo1", "system": "Forked repository user1/repo1 successfully! Fork URL: https://github.com/<OWNER>/repo1" }, { "action": "CREATE_PULL_REQUEST", "user": "Create a pull request on repository <OWNER>/repo1 with branch 'feature/improve-ux', title 'Improve user experience' against base 'main'", "system": "Pull request created successfully! URL: https://github.com/user1/repo1/pull/<PR_NUMBER> @ branch: 'feature/improve-ux'", }, { "action": "MERGE_PULL_REQUEST", "user": "Merge pull request #1 in repository user1/repo1 using merge method 'squash'", "system": "Merged pull request #1 successfully!" }, { "action": "CLOSE_ISSUE", "user": "Close issue #1 in repository user1/repo1", "system": "Closed issue #1 successfully!" } ]Example 2: Bug resolution
User: "There's a critical bug in the login system of user1/repo1 that needs to be fixed immediately."
[ { "action": "INITIALIZE_REPOSITORY", "user": "Initialize the repository user1/repo1 on main branch", "system": "Repository initialized successfully! URL: https://github.com/user1/repo1" }, { "action": "CREATE_MEMORIES_FROM_FILES", "user": "Create memories from files on repository user1/repo1 @ branch main and path '/'", "system": "Memories created successfully!" }, { "action": "CREATE_ISSUE", "user": "Create an issue in repository user1/repo1 titled 'Critical Bug: Login System Failure'", "system": "Created issue #<ISSUE_NUMBER> successfully!" }, { "action": "MODIFY_ISSUE", "user": "Update issue #1 in repository user1/repo1 to add the label 'bug'", "system": "Modified issue #1 successfully!" }, { "action": "GENERATE_CODE_FILE_CHANGES", "user": "Generate code file changes to fix the login system in repository user1/repo1", "system": "Here are the list of code file changes to be made to fix the login system in repository user1/repo1:\n\n1. **<FILE_PATH_1>**: ```\n<FILE_CONTENT_1>\n```\n2. **<FILE_PATH_2>**: ```\n<FILE_CONTENT_2>\n```\n3. **<FILE_PATH_3>**: ```\n<FILE_CONTENT_3>\n```\n4. etc." }, { "action": "CREATE_COMMIT", "user": "Create a commit in the repository user1/repo1 on branch 'fix/login-system' with the commit message: 'Fix: Login system critical bug'", "system": "Changes commited to repository user1/repo1 successfully to branch 'fix/login-system'! commit hash: <COMMIT_HASH>" }, { "action": "FORK_REPOSITORY", "user": "Fork repository user1/repo1", "system": "Forked repository user1/repo1 successfully! Fork URL: https://github.com/<OWNER>/repo1" }, { "action": "CREATE_PULL_REQUEST", "user": "Create a pull request on repository <OWNER>/repo1 with branch 'fix/login-system', title 'Fix: Login System Critical Bug' against base 'main'", "system": "Pull request created successfully! URL: https://github.com/user1/repo1/pull/<PR_NUMBER> @ branch: 'fix/login-system'" }, { "action": "MERGE_PULL_REQUEST", "user": "Merge pull request #1 in repository user1/repo1 using merge method 'squash'", "system": "Merged pull request #1 successfully!" }, { "action": "CLOSE_ISSUE", "user": "Close issue #1 in repository user1/repo1", "system": "Closed issue #1 successfully!" } ]Example 3: Documentation update
User: "Update the architecture documentation in octocat/hello-world."
[ { "action": "INITIALIZE_REPOSITORY", "user": "Initialize the repository octocat/hello-world on main branch", "system": "Repository initialized successfully! URL: https://github.com/octocat/hello-world" }, { "action": "CREATE_MEMORIES_FROM_FILES", "user": "Create memories from files on repository octocat/hello-world @ branch main and path '/'", "system": "Memories created successfully!" }, { "action": "IDEATION", "user": "Ideate on improving the architecture of octocat/hello-world", "system": "Analyzing the repository and considering previous user feedback, here are some architecture improvement ideas:\n\n1. **<IDEA_TITLE_1>**: <IDEA_DESCRIPTION_1>\n2. **<IDEA_TITLE_2>**: <IDEA_DESCRIPTION_2>\n3. **<IDEA_TITLE_3>**: <IDEA_DESCRIPTION_3>\n4. etc." }, { "action": "CREATE_ISSUE", "user": "Create an issue in repository octocat/hello-world titled 'Update: Architecture Documentation'", "system": "Created issue #<ISSUE_NUMBER> successfully!" }, { "action": "GENERATE_CODE_FILE_CHANGES", "user": "Generate code file changes to update the architecture documentation in repository octocat/hello-world", "system": "Here are the list of code file changes to be made to update the architecture documentation in repository octocat/hello-world:\n\n1. **<FILE_PATH_1>**: ```<FILE_CONTENT_1>```\n2. **<FILE_PATH_2>**: ```<FILE_CONTENT_2>```\n3. **<FILE_PATH_3>**: ```<FILE_CONTENT_3>```\n4. etc." }, { "action": "CREATE_COMMIT", "user": "Create a commit in the repository octocat/hello-world on branch 'docs/architecture-update' with the commit message: 'docs: Update Architecture Documentation'", "system": "Changes commited to repository octocat/hello-world successfully to branch 'docs/architecture-update'! commit hash: <COMMIT_HASH>" }, { "action": "FORK_REPOSITORY", "user": "Fork repository octocat/hello-world", "system": "Forked repository octocat/hello-world successfully! Fork URL: https://github.com/<OWNER>/hello-world" }, { "action": "CREATE_PULL_REQUEST", "user": "Create a pull request on repository <OWNER>/hello-world with branch 'docs/architecture-update' against base 'main', title 'docs: Update Architecture Documentation' and files 'docs/architecture.md'", "system": "Pull request created successfully! URL: https://github.com/octocat/hello-world/pull/<PR_NUMBER> @ branch: 'docs/architecture-update'" }, { "action": "REACT_TO_PULL_REQUEST", "user": "React to pull request #1 in repository octocat/hello-world with a thumbs up", "system": "Added reaction to pull request #1 successfully!" }, { "action": "MERGE_PULL_REQUEST", "user": "Merge pull request #1 in repository octocat/hello-world using merge method 'squash'", "system": "Merged pull request #1 successfully!" }, { "action": "CLOSE_ISSUE", "user": "Close issue #1 in repository octocat/hello-world", "system": "Closed issue #1 successfully!" } ]The text was updated successfully, but these errors were encountered: