Skip to content

chore(agents): Add dotagents#19526

Open
chargome wants to merge 3 commits intodevelopfrom
cg/dotagents-init
Open

chore(agents): Add dotagents#19526
chargome wants to merge 3 commits intodevelopfrom
cg/dotagents-init

Conversation

@chargome
Copy link
Member

@chargome chargome commented Feb 25, 2026

Closes #19527 (added automatically)

@chargome chargome self-assigned this Feb 25, 2026
@@ -0,0 +1 @@
../.agents/skills No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The triage-issue.yml workflow references Python scripts from the triage-issue skill, which have been deleted in this PR, causing the workflow to fail.
Severity: HIGH

Suggested Fix

Either restore the deleted triage-issue skill files, move them to the new .agents/skills/ directory and update the paths in .github/workflows/triage-issue.yml, or disable the workflow if the skill is no longer needed.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .claude/skills#L1

Potential issue: The `.github/workflows/triage-issue.yml` workflow is configured to run
on new issues with specific labels. This workflow contains hardcoded paths to Python
scripts, such as `.claude/skills/triage-issue/scripts/write_job_summary.py`, which were
part of the `triage-issue` skill. Since this skill and its associated files have been
completely removed in this pull request, the workflow will fail with a "file not found"
error whenever it is triggered. This will break the automated issue triage process for
the repository.

Did we get this right? 👍 / 👎 to inform future reviews.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 25, 2026

size-limit report 📦

Path Size % Change Change
@sentry/browser 25.62 kB - -
@sentry/browser - with treeshaking flags 24.12 kB - -
@sentry/browser (incl. Tracing) 42.42 kB - -
@sentry/browser (incl. Tracing, Profiling) 47.09 kB - -
@sentry/browser (incl. Tracing, Replay) 81.24 kB - -
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 70.86 kB - -
@sentry/browser (incl. Tracing, Replay with Canvas) 85.94 kB - -
@sentry/browser (incl. Tracing, Replay, Feedback) 98.2 kB - -
@sentry/browser (incl. Feedback) 42.43 kB - -
@sentry/browser (incl. sendFeedback) 30.29 kB - -
@sentry/browser (incl. FeedbackAsync) 35.34 kB - -
@sentry/browser (incl. Metrics) 26.79 kB - -
@sentry/browser (incl. Logs) 26.93 kB - -
@sentry/browser (incl. Metrics & Logs) 27.61 kB - -
@sentry/react 27.37 kB - -
@sentry/react (incl. Tracing) 44.76 kB - -
@sentry/vue 30.07 kB - -
@sentry/vue (incl. Tracing) 44.27 kB - -
@sentry/svelte 25.64 kB - -
CDN Bundle 28.16 kB - -
CDN Bundle (incl. Tracing) 43.25 kB - -
CDN Bundle (incl. Logs, Metrics) 29 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) 44.09 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) 68.08 kB - -
CDN Bundle (incl. Tracing, Replay) 80.13 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) 80.99 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) 85.64 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) 86.53 kB - -
CDN Bundle - uncompressed 82.34 kB - -
CDN Bundle (incl. Tracing) - uncompressed 128.06 kB - -
CDN Bundle (incl. Logs, Metrics) - uncompressed 85.18 kB - -
CDN Bundle (incl. Tracing, Logs, Metrics) - uncompressed 130.89 kB - -
CDN Bundle (incl. Replay, Logs, Metrics) - uncompressed 208.84 kB - -
CDN Bundle (incl. Tracing, Replay) - uncompressed 244.94 kB - -
CDN Bundle (incl. Tracing, Replay, Logs, Metrics) - uncompressed 247.76 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 257.85 kB - -
CDN Bundle (incl. Tracing, Replay, Feedback, Logs, Metrics) - uncompressed 260.66 kB - -
@sentry/nextjs (client) 47.17 kB - -
@sentry/sveltekit (client) 42.88 kB - -
@sentry/node-core 52.18 kB +0.02% +7 B 🔺
@sentry/node 173.46 kB +0.01% +10 B 🔺
@sentry/node - without tracing 97.33 kB +0.02% +10 B 🔺
@sentry/aws-serverless 113.13 kB +0.01% +7 B 🔺

View base workflow run

@@ -0,0 +1 @@
../.agents/skills No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triage-issue skill deleted, breaking CI workflow

High Severity

.claude/skills is replaced with a symlink to ../.agents/skills, and all triage-issue skill files are deleted, but the skill was never re-created under .agents/skills/triage-issue/ nor declared in agents.toml. The GitHub Actions workflow in .github/workflows/triage-issue.yml still references paths like .claude/skills/triage-issue/scripts/detect_prompt_injection.py and other scripts, which will now resolve to nonexistent files. This completely breaks the automated issue triage CI pipeline.

Fix in Cursor Fix in Web

@@ -0,0 +1 @@
../.agents/skills No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The triage-issue.yml workflow uses hardcoded paths for scripts that have been moved. The added symlink is unlikely to work in GitHub Actions, which will cause the workflow to fail.
Severity: CRITICAL

Suggested Fix

Update the hardcoded paths in the .github/workflows/triage-issue.yml file to point directly to the new script locations under .agents/skills/triage-issue/scripts/. This removes the reliance on the symlink, which is unreliable in the GitHub Actions execution environment.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .claude/skills#L1

Potential issue: The `.github/workflows/triage-issue.yml` workflow file contains
hardcoded paths to Python scripts that were previously located in
`.claude/skills/triage-issue/scripts/`. These scripts have been moved to
`.agents/skills/triage-issue/scripts/`. While a symlink from `.claude/skills` to
`../.agents/skills` has been added, symlinks are often not resolved correctly in GitHub
Actions environments and can be treated as plain text files. As a result, the workflow
will fail at runtime when it attempts to execute the scripts from their old,
now-nonexistent locations, breaking the automated issue triage functionality.

@@ -0,0 +1 @@
../.agents/skills No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The triage-issue workflow relies on a new .claude/skills symlink to find scripts. If the symlink fails in the runner environment, the workflow will break.
Severity: MEDIUM

Suggested Fix

Update the paths in .github/workflows/triage-issue.yml to directly reference the new script location at .agents/skills/. This removes the dependency on the symlink's behavior in the runner environment. Alternatively, verify the symlink is correctly created with Git mode 120000 and add error handling to the workflow to catch path resolution failures.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .claude/skills#L1

Potential issue: The `triage-issue.yml` workflow executes Python scripts that were
previously located in `.claude/skills/triage-issue/scripts/`. These scripts have been
moved to `.agents/skills/`, and a symlink named `.claude/skills` has been created to
point to the new directory. However, the workflow file has not been updated to use the
new path. If the Git symlink is not properly created or does not function as expected
within the GitHub Actions runner environment, commands attempting to execute the
scripts, such as `python3 .claude/skills/triage-issue/scripts/write_job_summary.py`,
will fail with a "file not found" error. This will cause the triage workflow to fail
silently during the summary generation step.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

# Check skills into git so collaborators get them without running 'dotagents install'.
# Set to true (or remove) to gitignore managed skills instead.
gitignore = false
agents = ["claude", "cursor"]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing .cursor/skills symlink despite cursor agent configured

Medium Severity

agents.toml declares agents = ["claude", "cursor"], and the .claude/skills symlink to ../.agents/skills was committed, but no corresponding .cursor/skills symlink exists. The dotagents documentation in this same PR states both Claude and Cursor get <agent-dir>/skills/ symlinks. The .cursor/ directory already exists with commands and rules, but Cursor users won't discover skills from .agents/skills/ without the symlink.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(agents): Add dotagents

1 participant