Best for
- Use this skill when a user wants cleaner code, a more direct implementation, or a readability pass that preserves exact functionality.
yun520-1/mark-heartflow-skill/skills/simplify/SKILL.md
Refactor code for clarity, consistency, and maintainability without changing behavior. Use when the user types /simplify or asks to simplify code.
Decision brief
Refactor code to make it easier to read, simpler to maintain, and more consistent with the surrounding codebase without changing what it does.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/yun520-1/mark-heartflow-skill --skill "skills/simplify"Inspect the Agent Skill "simplify" from https://github.com/yun520-1/mark-heartflow-skill/blob/20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c/skills/simplify/SKILL.md at commit 20bbbb4eacf56c941ddc3420dcbc81c04d55ec5c. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Use this skill when a user wants cleaner code, a more direct implementation, or a readability pass that preserves exact functionality.
Preserve functionality. Never change behavior, outputs, side effects, or public interfaces unless the user explicitly asks for that.
Focus on recently modified code unless the user points to a different file, module, or diff.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 52/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 36 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Refactor code to make it easier to read, simpler to maintain, and more consistent with the surrounding codebase without changing what it does.
Invoke this skill with /simplify.
Use this skill when a user wants cleaner code, a more direct implementation, or a readability pass that preserves exact functionality.
Preserve functionality. Never change behavior, outputs, side effects, or public interfaces unless the user explicitly asks for that.
Apply project standards. Match the existing conventions, patterns, naming style, and architectural expectations of the codebase.
Reduce unnecessary complexity. Flatten avoidable nesting, remove redundant abstractions, and prefer the most direct implementation that remains clear.
Keep variables intentional. Avoid introducing extra state unless it materially improves readability or is reused enough to justify it.
Improve naming and structure. Prefer clear variable and function names, and group related logic so the code reads in a straightforward way.
Focus on recently modified code unless the user points to a different file, module, or diff.
Inspired by the new Claude Code /simplify command:
Alternatives
griffinwork40/agent-afk
Discovers incidental complexity, duplication, and dead code in a codebase and produces a ranked, behavior-preserving reduction plan — optionally applying safe changes. Dispatches four parallel read-only discovery lenses (clone detection, dead code, complexity hotspots, wrong abstraction), synthesizes into a prioritized reduction plan, and gates apply mode behind /refactor and a hard test check.
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
event4u-app/agent-config
Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.
event4u-app/agent-config
Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.