All authors

Claude Skills by MongLong0214
github.com/MongLong021416 skills0 installs27 views
- CommitsCapture a decision record from verified session and diff evidence before a commit.Votes: 0GitHub stars: 18
- QueryRead recorded constraints before changing a repository path.Votes: 0GitHub stars: 18
- SetupSet up CommitLore in a repository when the operator asks for it.Votes: 0GitHub stars: 18
- Commitlore CodexUse when reading or changing a repository would benefit from its recorded decision history, or when a commit may need verified decision context. Query before edits, guard against previously rejected approaches, and capture supported records before committing.Votes: 0GitHub stars: 18
- Commitlore CommitsUse when about to make a git commit and there is decision context worth recording — a constraint that shaped the change, an alternative that was tried and dropped, a warning for whoever touches this next. Drives the CommitLore capture pipeline, which drafts a record from the session transcript and the staged diff, machine-checks every quote against them, and binds what survives to the commit it was prepared for. Applies to an ordinary commit request, not only to one that names CommitLore: mos...Votes: 0GitHub stars: 18
- Commitlore QueryUse when about to read, edit, or reason about a file and it would help to know its recorded decision history — active constraints, alternatives already ruled out, warnings left by a previous author, or which records have gone stale. Reads CommitLore records for a path or the whole repo without re-deriving them from raw git log. Trigger phrases include "what does commitlore know about this file", "why was X ruled out here", "any warnings on this path", "check for stale records", "has this appr...Votes: 0GitHub stars: 18
- Commitlore SetupUse when a git repository needs CommitLore wired up for the first time, or when its hook/notes configuration looks broken. Runs the diagnostic, installs the commit-msg validation hook, fixes the notes fetch refspec so records survive a clone or fetch, and builds the local record index. Trigger phrases include "set up commitlore in this repo", "install the commitlore hook", "commitlore doctor is warning", "why isn't commitlore capturing commits here", "wire up commit trailers", "commitlore 저장소...Votes: 0GitHub stars: 18
- EvidenceGather exact source evidence for the current question with the jev_evidence tool, instead of reading whole files.Votes: 0GitHub stars: 3
- Jev GateUse Jev Gate policies and exact repository evidence in native Codex. Use for locating source evidence, reading verified source windows, or diagnosing the Jev Gate Codex plugin. Automatic policies require the native session connection.Votes: 0GitHub stars: 3
- Code ReviewerReviews a diff or a file for defects. Use when asked to review code, check a pull request, look for bugs, assess code quality, or give feedback on an implementation. Triggers include "review this", "code review", "PR 리뷰", "코드 리뷰", "버그 있는지 봐줘".Votes: 0GitHub stars: 2
- Release PlannerPlans and documents software releases. Use when preparing a release, writing a rollout or deployment plan, defining release phases, cutting a release branch, drafting release notes, or coordinating a staged rollout. Triggers include "release", "rollout", "deploy plan", "release notes", "출시", "배포 계획", "릴리스".Votes: 0GitHub stars: 2
- Security ReviewFinds and fixes security vulnerabilities in application code. Use when asked about injection, XSS, CSRF, authentication or authorization flaws, secret handling, unsafe deserialization, or when hardening an endpoint. Triggers include "vulnerability", "SQL injection", "취약점", "보안", "인증 우회".Votes: 0GitHub stars: 2
- Test WriterWrites unit and integration tests. Use when asked to add tests, improve coverage, write a regression test for a bug, or set up a test file for existing code. Triggers include "write tests", "unit test", "regression test", "테스트 작성", "테스트 코드", "커버리지".Votes: 0GitHub stars: 2
- Frontier Simplify AuditDiagnoses a repository that has accumulated agent-built bureaucracy. Measures how much of the codebase exists to police the work rather than do it, finds the maintenance loops that produce commits with no product value, and ranks what to delete. Use when the user says "audit this repo for ceremony", "why is this repo so slow", "we spend all our time on tooling", "find the bureaucracy", "frontier-simplify-audit", or when a project is visibly stalled on its own gates and validators. One-shot re...Votes: 0GitHub stars: 2
- Frontier Simplify ReviewReview a change for concrete defects, then check repairs and their regressions against the preserved review. Use for substantial PR reviews or repeated review rounds. Stops automatic review after at most three attempts per PR and hands off; does not guarantee safe merge convergence.Votes: 0GitHub stars: 2
- Frontier SimplifyStops an agent from manufacturing process around its own work — invented gates, approval flows, traceability matrices, verification machinery, and governance documents nobody asked for. Use when producing any document, plan, PRD, spec, design doc, ticket, ADR, or roadmap; when setting up a repository, workflow, or CI; when adding a check, validator, or gate; and whenever work has stalled on its own tooling. Triggers include "frontier-simplify", "PRD", "spec", "design doc", "plan this", "roadm...Votes: 0GitHub stars: 2