You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cursor-agent -p "You are operating in a GitHub Actions runner to automatically update llms.txt and llms-full.txt files.
70
75
71
76
The GitHub CLI is available as \`gh\` and authenticated via \`GH_TOKEN\`. Git is available. You have write access to repository contents and can comment on pull requests, but you must not create or edit PRs directly.
72
77
73
-
IMPORTANT: Before starting your analysis, use the run_terminal_cmd tool to execute:
If this command returns any results, use run_terminal_cmd to post a cancellation comment on the PR and then use run_terminal_cmd to execute 'exit 0'. Otherwise, proceed with your analysis.
81
+
If this returns any results, immediately post a cancellation comment and exit. Otherwise, proceed with your analysis.
This is a docs repository with the following main directories that each contain llms.txt and llms-full.txt files:
@@ -98,17 +103,16 @@ jobs:
98
103
Analyze changes in the original PR and determine if they are significant enough to warrant updating the llms.txt and llms-full.txt files for the affected directories. If so, create a separate PR with the updates.
99
104
100
105
# Requirements:
101
-
1) Use run_terminal_cmd to execute \`gh pr diff ${PR_NUMBER}\` to analyze what changed in the original PR
106
+
1) Use \`gh pr diff\` to analyze what changed in the original PR
102
107
2) Determine which documentation directories are affected by the changes
103
108
3) Assess if the changes are significant enough to update the llms.txt files (new content, major restructuring, new features, etc.)
104
109
4) If changes are significant:
105
-
- Use run_terminal_cmd to create or update a persistent branch named \`${BRANCH_PREFIX}/pr-${PR_NUMBER}\`
106
-
- Use read_file to read existing llms.txt and llms-full.txt files
107
-
- Use search_replace or write to update the relevant llms.txt and llms-full.txt files
108
-
- Use run_terminal_cmd to push the changes to the branch
109
-
- Use run_terminal_cmd to comment on the original PR with a summary and a compare link
110
+
- Create or update a persistent branch named \`${{ env.BRANCH_PREFIX }}/pr-${{ github.event.pull_request.number }}\`
111
+
- Update the relevant llms.txt and llms-full.txt files to reflect the new documentation structure and content
112
+
- Push the changes to the branch
113
+
- Comment on the original PR with a summary and a compare link to create the PR
110
114
5) If changes are not significant:
111
-
- Use run_terminal_cmd to comment on the original PR explaining that no llms.txt updates are needed
115
+
- Comment on the original PR explaining that no llms.txt updates are needed
112
116
113
117
# File Format Guidelines:
114
118
- llms.txt files should be concise, focused summaries with key links
@@ -129,7 +133,4 @@ jobs:
129
133
- If updates needed: Pushed commits to the persistent branch and a PR comment with compare link
130
134
- If no updates needed: A brief comment explaining why no updates are required
131
135
- Keep all changes minimal and consistent with existing documentation style
132
-
- Keep the changes to the minimum necessary to update the llms.txt and llms-full.txt files
133
-
134
-
CRITICAL: After completing ANY of the above actions (stop command, updates completed, or no updates needed), wait 30 seconds and then terminate the process. Do not continue running or use any more tools.
0 commit comments