Skip to content

Commit 4e673c6

Browse files
fix: make it sarcastic
1 parent d285a6e commit 4e673c6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

website/blog/how-to-debug.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@ head:
2020

2121
# How to Debug ast-grep Rule Effectively
2222

23+
:::tip Let Claude Debug For You
24+
If you prefer not to debug manually, try the [ast-grep Claude skill](https://github.com/ast-grep/claude-skill). It can explain AST structures, identify why rules don't match, and suggest fixes—all through natural conversation.
25+
:::
26+
2327
Debugging ast-grep rules can be frustrating. You write what looks like a perfectly reasonable rule, test it against your code, and... nothing matches. Or worse, it matches things you didn't expect.
2428

2529
The key to effective debugging is one word: **SIMPLIFY**.
@@ -305,8 +309,4 @@ When a rule unexpectedly fails to match:
305309

306310
5. **Use the right tools.** The [online playground](https://ast-grep.github.io/playground.html) provides instant feedback and AST visualization. Use it liberally.
307311

308-
:::tip Let Claude Debug For You
309-
If you prefer not to debug manually, try the [ast-grep Claude skill](https://github.com/ast-grep/claude-skill). It can explain AST structures, identify why rules don't match, and suggest fixes—all through natural conversation.
310-
:::
311-
312312
Happy debugging!

0 commit comments

Comments
 (0)