Antfu
oyjt/uniapp-vue3-template
Anthony Fu's {Opinionated} preferences and best practices for web development
코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행. An agent skill from JiHong88/suneditor.
Install Post Edit
$ npx skills add JiHong88/suneditor --skill post-edit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JiHong88/suneditor post-edit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/post-edit .claude/skills/post-edit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .claude/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-editType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JiHong88/suneditor --skill post-edit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JiHong88/suneditor post-edit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/post-edit .agents/skills/post-edit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .agents/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JiHong88/suneditor --skill post-edit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JiHong88/suneditor post-edit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/post-edit .cursor/skills/post-edit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .cursor/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JiHong88/suneditor.git --path .agents/skills/post-edit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JiHong88/suneditor --skill post-edit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JiHong88/suneditor post-edit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/post-edit .gemini/skills/post-edit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .gemini/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JiHong88/suneditor post-editInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JiHong88/suneditor --skill post-edit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/post-edit .github/skills/post-edit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .github/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JiHong88/suneditor --skill post-edit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JiHong88/suneditor post-edit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JiHong88/suneditor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/post-edit .opencode/skills/post-edit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "post-edit" agent skill from https://github.com/JiHong88/suneditor/tree/master/.agents/skills/post-edit into .opencode/skills/post-edit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-edit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
post-edit- GitHub stars
- 2k
- Token cost
- ~829 tokens
- SKILL.md length
- 422 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행. An agent skill from JiHong88/suneditor.
- Works in 9 steps: npx --no-install eslint ; use --fix on… → npm run ts-build — generates types and… → npm run lint:type — required separately:… → …
- Tasks that involve Linting and formatting
- SKILL.md covers Scope and Source pipeline
- Calls npm, git and npx
What it does
Post Edit is an agent skill from JiHong88/suneditor. 코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. It works with npm and Git. The repository describes itself as: A lightweight and powerful WYSIWYG editor in vanilla JavaScript. No dependencies. The licence is MIT.
When your agent uses it
- Tasks that involve Linting and formatting
Example prompts
- “/post-edit”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Bash
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- npx --no-install eslint ; use --fix on those files if necessary.
- npm run ts-build — generates types and runs check:inject (writes generated sections).
- npm run lint:type — required separately: ts-build contains tsc || true, so generation
- npm run check:arch — import/cycle rules including L3 isolation; review runtime access and allowed-edge symbols.
- npm run check:exports — export sync.
- npm test -- --runInBand — Jest unit AND integration suites.
- Targeted browser tests for native input, selection, IME, iframe, layout or focus changes
- For new features/hot paths/resources, use prompts/performance-guide.md to check the
- git diff --check and inspect final status/diff, including generated artifacts. Do not
What it can do on your machine
Read from SKILL.md and the folder at commit 9de619b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmgitnpxtsc
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, git and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Post Edit loads about 829 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 422 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JiHong88/suneditor at commit 9de619b, republished under its MIT licence (© JiHong88). 422 words, ~829 tokens.
Download SKILL.mdSave it as
.claude/skills/post-edit/SKILL.md (or your agent's skills folder).- name
- post-edit
- description
- 코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행
- allowed-tools
- Bash
Validate the intended changes without rewriting unrelated work. Read git status --short,
git diff and git diff --cached first. Never stage, restore or stash to prepare validation.
Scope
- Documentation/harness-only: run
npm run check:harness, verify changed API examples at their source, thengit diff --check. Skip source lint, generation and runtime tests. - Source JS: run the sequence below. Fix formatting only in the changed source files;
do not start with the repository-wide
lint:fix-jsautofixer on unrelated user work. - CSS/layout: lint applicable files, build with
npm run build:prod, and run relevant browser cases. Source-only Jest cannot establish layout correctness. - Test/tooling-only: run the changed tool or relevant test suite and applicable static checks.
For dependency rules, run both
npm run check:archandnpm run test:arch. Commands and CI scope: Testing and Validation.
Source pipeline
Run sequentially; stop dependent steps on failure, diagnose and rerun only affected checks:
npx --no-install eslint <changed-source-files>; use--fixon those files if necessary.npm run ts-build— generates types and runscheck:inject(writes generated sections).npm run lint:type— required separately:ts-buildcontainstsc || true, so generation exit code alone does not establish type correctness.npm run check:arch— import/cycle rules including L3 isolation; review runtime access and allowed-edge symbols.npm run check:exports— export sync.npm test -- --runInBand— Jest unit AND integration suites.- Targeted browser tests for native input, selection, IME, iframe, layout or focus changes:
npm run test:e2e -- <relevant-spec> --project=chromium. Use the configured Firefox project for relevant*.firefox.spec.jscases. For geometry/direction, runnpm run test:browser -- geometry.spec.js(DIV/iframe × LTR/RTL in Chromium and Firefox). State any untested browser/device behavior. - For new features/hot paths/resources, use
prompts/performance-guide.mdto check the relevant costs and lifecycle; runnpm run test:perffor selection/offset paths. Extend the benchmark for other hot paths rather than claiming existing coverage. Report fixture/operation/metric. git diff --checkand inspect final status/diff, including generated artifacts. Do not discard unexpected changes with git; identify their source and report them.
Show full SKILL.md (99 more words)Show less
Use npm run build:prod additionally when bundling, exports, assets or new plugin imports
change. Reuse successful checks from this same task if their inputs have not changed.
check:langs is excluded from automatic validation: it uses Google translation credentials
and writes translations. For en.js changes, follow prompts/editing-rules.md and report
whether translation was actually run. Do not claim a skipped step passed.
Report each applicable step as pass/fail/skipped (with reason), test counts, and any remaining failure. Check causal relevance before calling a failure pre-existing; use an isolated worktree for baseline evidence when needed. Never alter the user's index or shared WIP.
© JiHong88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/post-edit of JiHong88/suneditor.
Open the folder on GitHubat commit 9de619b
Compare with similar skills
Post Edit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Post Edit this skillJiHong88/suneditor | 2k | — | ~829 | Automated safety check: Notes | MIT | |
| Antfuoyjt/uniapp-vue3-template | 627 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Obsidian Plugin Releasecrafter-station/skills | 112 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Git PR Workflowandymai/brepjs | 115 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Devserithemage/serverless-openclaw | 196 | — | ~714 | Automated safety check: Notes | None | |
| Quality Gatesandymai/brepjs | 115 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Obsidian Plugin Release
crafter-station/skills
Release a new version of an Obsidian community plugin without forgetting steps.
Git PR Workflow
andymai/brepjs
This skill should be used when committing, pushing, branching, or merging in the brepjs repository — when a task involves "pre-commit hook failed" (which tier ran, how to bypass), "commit rejected…
Dev
serithemage/serverless-openclaw
Development workflow guide. An agent skill from serithemage/serverless-openclaw.
Quality Gates
andymai/brepjs
This skill should be used when a local brepjs quality gate or npm run validate step fails and the specific rule's fix or escape hatch is needed — ESLint errors like "no-explicit-any" or "Direct .oc…
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
More from JiHong88/suneditor
Commit
JiHong88/suneditor
커밋 메시지를 자동 생성하고 커밋한다. An agent skill from JiHong88/suneditor.
Code Review
JiHong88/suneditor
코드 리뷰 — 버그, 로직 오류, 성능 회귀, 수명 관리 및 프로젝트 규칙 위반 검출. An agent skill from JiHong88/suneditor.
Changes
JiHong88/suneditor
수동 코드 수정 후 changes.md에 누락된 변경사항 추가
Release Note
JiHong88/suneditor
changes.md를 릴리즈 노트 형식으로 변환
Related
Categories
Questions about Post Edit
What does Post Edit do?
코드 수정 후 범위에 맞는 lint, 타입 검사, 빌드 검증, 동작 및 성능 테스트 실행. An agent skill from JiHong88/suneditor. Post Edit is an agent skill from JiHong88/suneditor.
When should I use Post Edit?
Post Edit fits situations like: tasks that involve Linting and formatting.
How do I install Post Edit in Claude Code?
Run `npx skills add JiHong88/suneditor --skill post-edit -a claude-code`. Or copy the skill folder (.agents/skills/post-edit in JiHong88/suneditor) into .claude/skills/post-edit in your project. Claude Code loads it when a task matches its description.
How do I install Post Edit in Codex?
Run `npx skills add JiHong88/suneditor --skill post-edit -a codex`. Or copy the skill folder (.agents/skills/post-edit in JiHong88/suneditor) into .agents/skills/post-edit in your project. Codex loads it when a task matches its description.
Can I use Post Edit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JiHong88/suneditor --skill post-edit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-edit, .gemini/skills/post-edit, .github/skills/post-edit and .opencode/skills/post-edit in your project.
What does Post Edit need to run?
Going by SKILL.md and its folder, Post Edit needs the command-line tools its instructions call (npm, git, npx and tsc). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash.
Does Post Edit access the network?
SKILL.md contains no URLs. Its commands use npm, git and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Post Edit safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Post Edit use?
Post Edit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Post Edit use?
About 829 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Post Edit?
Skills that share tags, products or a category with Post Edit: Antfu (oyjt/uniapp-vue3-template, 627 stars), Obsidian Plugin Release (crafter-station/skills, 112 stars), Git PR Workflow (andymai/brepjs, 115 stars) and Dev (serithemage/serverless-openclaw, 196 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post Edit?
JiHong88 (a GitHub user) maintains it in JiHong88/suneditor, which has 2,019 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: JiHong88/suneditor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.