writing-korean
Skill0 starsChanged 6 months agoNo licenceView on GitHub
Use when writing or revising Korean prose that a person will read (PR or commit bodies, Slack or status reports, runbooks, Confluence pages, design docs, review replies), or when asked to 다듬어, 자연스럽게, AI 티 없애 Korean text. Especially when turning a long session's terse notes into a report for someone outside the conversation.
In this repository22 other files it gives its agents.
- brainstormingSkill
- building-dev-imagesSkill
- commit-push-prSkill
- commit-pushSkill
- commitSkill
- copilot-review-loopSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- receiving-code-review-autoSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- review-with-google-mindSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-ops-runbooksSkill
- writing-plansSkill
- writing-skillsSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.