[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SCG806PTTZB4VAFD09ZXV":3,"skill-same:01M79SCG806PTTZB4VAFD09ZXV":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M79SCG806PTTZB4VAFD09ZXV","ast-grep",null,"AST-aware structural code search and rewrite via ast-grep.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fast-grep\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ast-grep\ndescription: \"AST-aware structural code search and rewrite via ast-grep.\"\nversion: 1.1.0\nauthor: Yeongyu Kim (code-yeongyu), adapted by Hermes Agent, ported for CrusorAI\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [ast, codemod, refactoring, structural-search, code-search, rewrite, tree-sitter]\n    related_skills: [simplify-code, systematic-debugging]\n---\n\n**Triggers:** ast-grep, ast grep, codemod, structural search, structural replace, rewrite all, rewrite every, find all functions, every call site, code shape, sg run\n\n# ast-grep\n\n`ast-grep` (binary `sg`; on Linux prefer `ast-grep` — `sg` collides with `setgroups`) is an **AST-aware search and rewrite tool** across ~25 languages. It parses your pattern as code and matches structurally. Right tool whenever the question depends on **code shape**, not text bytes. Install: `run_terminal(\"npm i -g @ast-grep\u002Fcli\")` or `cargo install ast-grep` \u002F `pip install ast-grep-py`. Check with `sg --version`.\n\n## When to use (vs search_files)\n\n- \"Find every function that takes a `Request` parameter.\" → ast-grep\n- \"Rewrite every `console.log(x)` to `logger.info(x)`.\" → ast-grep\n- \"Migrate `Optional[X]` to `X | None`.\" \u002F \"Strip every `as any`.\" → ast-grep\n- String contents, comments, file names, cross-language regex → `search_files` \u002F `rg`\n\nAsk: \"does the answer depend on the syntax tree, or just the file's bytes?\"\n\n## Three things to internalize\n\n### 1. ast-grep is NOT regex\n\nWildcards are `$VAR` (one AST node) and `$$$` (zero or more nodes). Regex syntax fails silently: `foo|bar`, `.*foo`, `\\w+`, `[a-z]` are NOT patterns — run two searches, use `$VAR`, or switch to search_files.\n\n### 2. Patterns must be valid code\n\n`def $FN($$$):` fails (trailing `:` incomplete) → `def $FN($$$): $$$` with a body or `def $FN($$$)` for signature matching. `function $NAME` fails → `function $NAME($$$) { $$$ }`.\n\n### 3. `--update-all` and `--json` are mutually exclusive (silently)\n\nTo preview AND apply, run two passes:\n\n```bash\nsg run -p 'PATTERN' -r 'REWRITE' --json=compact .   # pass 1: preview\nsg run -p 'PATTERN' -r 'REWRITE' --update-all .     # pass 2: apply\n```\n\n## Core commands (through `run_terminal`, single-quote every pattern)\n\n```bash\n# Search\nsg run -p 'console.log($MSG)' --lang ts src\u002F\n# Search with JSON for scripting\nsg run -p 'console.log($MSG)' --lang ts --json=compact src\u002F\n# Rewrite — ALWAYS dry-run first\nsg run -p 'console.log($MSG)' -r 'logger.info($MSG)' --lang ts --json=compact src\u002F\n# Then apply, then review blast radius\nsg run -p 'console.log($MSG)' -r 'logger.info($MSG)' --lang ts --update-all src\u002F\ngit diff --stat\n# YAML lint rules (reusable rules in sgconfig.yml)\nsg scan src\u002F\n```\n\n`--lang` is required when piping via `--stdin` (no extension to infer). Use `tsx` for `.tsx` files — `--lang ts` will not parse JSX.\n\n## Rewriting discipline\n\n1. Search to confirm matches. 2. Dry-run rewrite (`--json=compact`). 3. Inspect: match count, files affected, per-location preview. 4. Wrong → refine, go to 1. 5. Right → `--update-all`, then `git diff --stat` before finishing. **Report the number of files affected, not just matches — users care about blast radius.** In Crusor, bulk rewrites are a mutation: surface the dry-run summary and get approval before `--update-all` when the mutation gate asks.\n\n## 0 matches but the code is there?\n\n1. Check the pattern for regex leakage (`\\w`, `.*`, `|`)\n2. Check `--lang` (ts vs tsx)\n3. Debug-parse: `echo '\u003Csample>' | sg run -p '\u003Cpattern>' --lang ts --debug-query=ast --stdin` — `ERROR` nodes mean a malformed pattern\n4. Inspect the target AST: `sg run -p '$_' --lang ts --debug-query=cst file.ts | head -40` to find the kind to match\n\n## Inline pattern vs YAML rules\n\nInline `-p` for one-off, simple, exploratory queries. YAML rules (under `rules\u002F`, `sg scan`) for reused lint rules, constraints\u002Ftransforms, auto-fix, snapshot tests.\n","**Triggers:** ast-grep, ast grep, codemod, structural search, structural replace, rewrite all, rewrite every, find all functions, every call site, code shape, sg run\n\n# ast-grep\n\n`ast-grep` (binary `sg`; on Linux prefer `ast-grep` — `sg` collides with `setgroups`) is an **AST-aware search and rewrite tool** across ~25 languages. It parses your pattern as code and matches structurally. Right tool whenever the question depends on **code shape**, not text bytes. Install: `run_terminal(\"npm i -g @ast-grep\u002Fcli\")` or `cargo install ast-grep` \u002F `pip install ast-grep-py`. Check with `sg --version`.\n\n## When to use (vs search_files)\n\n- \"Find every function that takes a `Request` parameter.\" → ast-grep\n- \"Rewrite every `console.log(x)` to `logger.info(x)`.\" → ast-grep\n- \"Migrate `Optional[X]` to `X | None`.\" \u002F \"Strip every `as any`.\" → ast-grep\n- String contents, comments, file names, cross-language regex → `search_files` \u002F `rg`\n\nAsk: \"does the answer depend on the syntax tree, or just the file's bytes?\"\n\n## Three things to internalize\n\n### 1. ast-grep is NOT regex\n\nWildcards are `$VAR` (one AST node) and `$$$` (zero or more nodes). Regex syntax fails silently: `foo|bar`, `.*foo`, `\\w+`, `[a-z]` are NOT patterns — run two searches, use `$VAR`, or switch to search_files.\n\n### 2. Patterns must be valid code\n\n`def $FN($$$):` fails (trailing `:` incomplete) → `def $FN($$$): $$$` with a body or `def $FN($$$)` for signature matching. `function $NAME` fails → `function $NAME($$$) { $$$ }`.\n\n### 3. `--update-all` and `--json` are mutually exclusive (silently)\n\nTo preview AND apply, run two passes:\n\n```bash\nsg run -p 'PATTERN' -r 'REWRITE' --json=compact .   # pass 1: preview\nsg run -p 'PATTERN' -r 'REWRITE' --update-all .     # pass 2: apply\n```\n\n## Core commands (through `run_terminal`, single-quote every pattern)\n\n```bash\n# Search\nsg run -p 'console.log($MSG)' --lang ts src\u002F\n# Search with JSON for scripting\nsg run -p 'console.log($MSG)' --lang ts --json=compact src\u002F\n# Rewrite — ALWAYS dry-run first\nsg run -p 'console.log($MSG)' -r 'logger.info($MSG)' --lang ts --json=compact src\u002F\n# Then apply, then review blast radius\nsg run -p 'console.log($MSG)' -r 'logger.info($MSG)' --lang ts --update-all src\u002F\ngit diff --stat\n# YAML lint rules (reusable rules in sgconfig.yml)\nsg scan src\u002F\n```\n\n`--lang` is required when piping via `--stdin` (no extension to infer). Use `tsx` for `.tsx` files — `--lang ts` will not parse JSX.\n\n## Rewriting discipline\n\n1. Search to confirm matches. 2. Dry-run rewrite (`--json=compact`). 3. Inspect: match count, files affected, per-location preview. 4. Wrong → refine, go to 1. 5. Right → `--update-all`, then `git diff --stat` before finishing. **Report the number of files affected, not just matches — users care about blast radius.** In Crusor, bulk rewrites are a mutation: surface the dry-run summary and get approval before `--update-all` when the mutation gate asks.\n\n## 0 matches but the code is there?\n\n1. Check the pattern for regex leakage (`\\w`, `.*`, `|`)\n2. Check `--lang` (ts vs tsx)\n3. Debug-parse: `echo '\u003Csample>' | sg run -p '\u003Cpattern>' --lang ts --debug-query=ast --stdin` — `ERROR` nodes mean a malformed pattern\n4. Inspect the target AST: `sg run -p '$_' --lang ts --debug-query=cst file.ts | head -40` to find the kind to match\n\n## Inline pattern vs YAML rules\n\nInline `-p` for one-off, simple, exploratory queries. YAML rules (under `rules\u002F`, `sg scan`) for reused lint rules, constraints\u002Ftransforms, auto-fix, snapshot tests.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":39,"description":7},"Yeongyu Kim (code-yeongyu), adapted by Hermes Agent, ported for CrusorAI","1.1.0",{"hermes":27},{"tags":28,"related_skills":36},[29,30,31,32,33,34,35],"ast","codemod","refactoring","structural-search","code-search","rewrite","tree-sitter",[37,38],"simplify-code","systematic-debugging",[40,41,42],"linux","macos","windows","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fast-grep","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill ast-grep",{"tool":56,"command":57},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill ast-grep",{"tool":59,"command":60},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill ast-grep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fast-grep\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]