fix(website): pin anchors and repair broken code fence in EN docs

- how-to/advanced/security.md: pin {#periodic-scanning} on 'Periodic
  Scanning', linked from this same page by anchor fragment.
- how-to/advanced/docker-sandbox.md: pin {#dev-profile} on 'Dev
  Profile', same reason.
- how-to/daily-tasks/organizing-skills.md: pin
  {#install-directly-into-folders} on that heading, same reason.
  Without an explicit id, translating the heading text changes its
  auto-generated slug and breaks the in-page link once translated.
- how-to/daily-tasks/creating-skills.md: the nested code-fence example
  under 'Include examples' used the same 3-backtick fence for both the
  outer block and the inner ```python block, so the inner fence's
  info string didn't count as a closer but the following bare fence
  did, silently truncating the outer block and leaving a dangling
  opener for the rest of the file. Widened the outer fence to 4
  backticks.
This commit is contained in:
Willie
2026-09-20 12:15:08 +08:00
parent 4415c7a75a
commit ec80c1df7c
4 changed files with 5 additions and 5 deletions
@@ -231,7 +231,7 @@ spec:
---
## Dev Profile
## Dev Profile {#dev-profile}
Two ways to develop the frontend with Vite HMR:
+1 -1
View File
@@ -171,7 +171,7 @@ rules:
For the full custom rules reference (merge semantics, disabling rules, exclude patterns), see [`audit rules` — Custom Rules](/docs/reference/commands/audit-rules#custom-rules).
### Periodic Scanning
### Periodic Scanning {#periodic-scanning}
Rules evolve — a skill that was clean at install time may match new rules added later. Schedule periodic scans:
@@ -75,7 +75,7 @@ Review the code and make it better.
```
**Include examples:**
```markdown
````markdown
## Example
User: "Review this function"
@@ -85,7 +85,7 @@ def add(a, b):
```
Response: Suggest adding type hints...
```
````
**Specify when NOT to use:**
```markdown
@@ -171,7 +171,7 @@ See [enable / disable](/docs/reference/commands/enable) and [.skillignore syntax
---
## Install Directly into Folders
## Install Directly into Folders {#install-directly-into-folders}
Use `--into` to install a skill into a subdirectory in one step — no manual `mv` needed: