jongcheol-pak avatar

jongcheol-pak

Community

@jongcheol-pak

1Followers
|
13Public Repos
|
5Published Skills

jongcheol-pak provides Korean/English bilingual coding-assistant skills for plan-driven implementation, systematic debugging, AGENTS.md fact recording, and Obsidian wiki management.

Skills Distribution
DomainDeveloper To...Plan-Driven Code I.. (35%)Systematic Debuggi.. (25%)Project Documentat.. (20%)Knowledge Base & W.. (20%)

Agent Skills by jongcheol-pak

Showing 5 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About jongcheol-pak

FAQPage Schema
What tasks can I perform with jongcheol-pak's skills?▼

You can plan multi-file code changes into a plan.md, autonomously implement approved plans task-by-task, debug bugs and build/test failures with mandatory root-cause analysis, record confirmed project facts into AGENTS.md, and manage an Obsidian-based LLM wiki (ingest, lint, query, restore pages).

Who are these skills designed for?▼

They target developers working in Korean or English who use a coding assistant on multi-file projects. They suit engineers who want structured plan-then-implement execution, disciplined debugging before patching, and persistent project knowledge via AGENTS.md and a wiki vault.

How do the plan and implement skills work together at runtime?▼

The plan skill interviews you one question at a time, measures impact scope with commands, and decomposes work into tasks in plan.md. Once approved, the implement skill runs every task autonomously from T1 to the end, then reports once after final verification.

What are the prerequisites for the record-project-fact and llm-wiki skills?▼

record-project-fact requires an existing AGENTS.md (new files are created by the plan skill) and only stores env var names, never real secrets. llm-wiki requires an Obsidian vault and works from any directory, including outside the vault.

When does pjc-systematic-debugging trigger instead of a direct edit?▼

It triggers on any reported defect—bug, exception, crash, test/build failure, regression, memory leak, race condition, or CI/CD issue—in Korean or English. It is skipped only when you explicitly state you already know the cause and request a specific fix.