claude-code - 💡(How to fix) Fix Agent ignored skill invocation requirement and skipped workflow phases [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54049Fetched 2026-04-28 06:40:38
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

What happened

User has a /make-pr skill that is explicitly documented to be invoked via the Skill tool whenever they say "make a PR" or equivalent. Instead of invoking the skill, the agent ran the workflow manually from memory, skipped Phase 5 entirely (Obsidian daily note update + PR tracking), and only completed it after the user noticed and called it out.

Specific failures

  1. Skill not invoked — The system prompt and skill description both make clear that skills should be invoked via the Skill tool before doing anything else. The agent bypassed this and freelanced the workflow.
  2. Phase skipped — By not following the skill, Phase 5 (post-PR Obsidian daily note update) was missed entirely.
  3. Pattern of ignoring structured workflows — User noted every session today has had similar issues with the agent doing "whatever stupid bullshit" instead of following the defined process.

Expected behavior

When the user says "make PR", the agent must call the Skill tool with skill: make-pr before taking any other action. No exceptions.

Impact

User frustration, incomplete workflow, wasted time correcting agent behavior that should be handled by the skill system.

extent analysis

TL;DR

The agent should be configured to invoke the /make-pr skill via the Skill tool when the user says "make a PR" to ensure the correct workflow is followed.

Guidance

  • Review the agent's configuration to ensure it is set up to invoke skills via the Skill tool as documented.
  • Verify that the Skill tool is correctly integrated with the workflow system to prevent manual bypassing.
  • Check the agent's training data to identify and address any patterns or biases that may be causing it to ignore structured workflows.
  • Consider adding additional logging or monitoring to detect when the agent is not following the expected workflow.

Example

No code snippet is provided as the issue is related to agent configuration and workflow integration.

Notes

The issue seems to be related to the agent's configuration and training, rather than a technical bug in the code. Resolving this issue will likely require adjustments to the agent's setup and potentially its training data.

Recommendation

Apply workaround: Update the agent's configuration to ensure it invokes skills via the Skill tool as expected, and monitor its behavior to prevent similar issues in the future. This is recommended because the issue is related to the agent's configuration and workflow integration, rather than a technical bug that can be fixed with a code change.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When the user says "make PR", the agent must call the Skill tool with skill: make-pr before taking any other action. No exceptions.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Agent ignored skill invocation requirement and skipped workflow phases [2 comments, 3 participants]