hylarucoder.
18 skills across 1 repo
- 100/100
ast-grep-rule-crafter
|
- 100/100
clean-code-reviewer
Produces a severity-rated (高/中/低) Clean Code findings report across 7 dimensions (naming, function size/SRP, duplication/DRY, over-engineering/YAGNI, magic numbers, structural clarity, project conventions), each with a location and a behavior-preserving refactor suggestion — never changing functionality. Use whenever the user asks for a code review, quality check, refactor advice, or code-smell / Clean Code analysis, OR points at a file/function/diff and asks if it is well-written, too long, too repetitive, over-engineered, or poorly named — even casually, and even if they never say "review" ("I just wrote this, look it over", "does this look good before I commit"). Trigger on 代码体检, 代码质量, 重构检查, 代码审查, 这段代码写得怎么样, 帮我看看代码有没有问题, 有没有坏味道, 这函数是不是太长了, 命名规范吗, 魔法数字, 重复代码, 过度设计, and English like "is this code clean", "any code smells", "check this file".
- 100/100
create-visual-card
|
- 100/100
entity-model-auditor
|
- 100/100
geju
|
- 100/100
goudi
|
- 100/100
hai-architecture
|
- 100/100
hai-audit-docs-against-code
|
- 100/100
hai-audit-docs-internally
|
- 100/100
hai-goal
|
- 100/100
hai-idea
|
- 100/100
hai-naming
|
- 100/100
hai-prd
|
- 100/100
hai-razor
|
- 100/100
hai-tdd
|
- 100/100
hai-visual-report
|
- 100/100
react-component-diagnosis
深度诊断单个 React 组件的架构设计质量,产出一份结构化体检报告:7 维度评分卡(使用者 API、数据流、可测试性、可扩展性、性能、心智模型、边界契约,每维 1-5 分 + 代码证据)、设计亮点、按 P0/P1/P2 分级且标注工作量的改进建议——所有评分基于逐行读代码后发现的具体问题(useMemo 依赖、useEffect cleanup、类型断言、每帧重复计算等),而非扫一眼目录得出的表面评价。当用户请求组件诊断、组件设计审查、架构分析、组件体检、组件 API/props 设计评估时使用,即使没说出"诊断"二字也应主动触发:用户指向一个组件目录或 .tsx 文件问"这个组件设计得怎么样"、"帮我看看这个组件"、"这个写得怎么样"、"是否需要重构"、"为什么每次都 re-render"、"useEffect 写对了吗"、"props 设计合理吗",或用英文说 "review this React component"、"is this component well designed"、"audit this component"、"should I refactor this component" 时,都应触发。触发词:组件诊断、组件体检、架构审查、设计分析、组件评审、组件 API、props 设计、组件要不要重构、component diagnosis、component review、react component audit。
- 100/100
readme-beautifier
README 美化器。接收结构混乱、格式不统一的 README(或同类 markdown 项目文档如 CONTRIBUTING.md、docs/index.md、项目说明.md),输出结构清晰、标题层级正确、列表/代码块/表格格式一致、视觉专业的完整版本,并附一段改动摘要——内容不增不减,只改结构和格式。当用户请求美化、整理、排版、格式化、修复 README,或只是把一份杂乱的 README 丢给你说"太乱了""看下""帮我弄一下"时使用,即使没有明确说"美化"二字。触发词:美化 README、README 美化、整理 README、README 排版、README 格式化、README 太乱了、看下我这个 README、beautify README、fix/format/clean up/tidy/polish/reformat README、reorganize readme、my readme looks messy/ugly、make my README look professional。