본문으로 건너뛰기
cccskills
무료GitHub에 공개

gh-commit

Review git changes and split them into semantic commits with clear messages. Use when the user asks to commit work, clean up local history, or group a mixed diff into logical commits. Do not commit on main or master unless the user explicitly asks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template스타 573(GitHub 573 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

  • SKILL.md2.2 KB
  • agents/openai.yaml198 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

GH Commit

Goal

Turn the current working tree into a small set of clean commits without mixing unrelated changes.

Workflow

  1. Verify git context.
  • Run git rev-parse --show-toplevel and git status -sb.
  • Read the branch with git branch --show-current.
  • If the branch is main or master, stop and ask the user to switch/create a branch (recommend codex/...) unless they explicitly asked to commit on that branch.
  1. Inspect all changes before staging anything.
  • Run git diff --stat and git diff --cached --stat.
  • List untracked files with git ls-files --others --exclude-standard.
  • Read actual hunks with git diff and git diff --cached.
  • Include untracked files in the review (read them if needed) so commit grouping decisions cover the full diff.
  1. Propose semantic commit groups.
  • Group by intent, not just file type (for example: bug fix, refactor, tests, docs).
  • Keep user-authored unrelated work separate.
  • Call out any files that need partial staging because they contain mixed concerns.
  1. Create each commit group.
  • Stage only the files or hunks for that group (git add <paths> or git add -p).
  • Verify exactly what is staged with git diff --cached --stat and git diff --cached.
  • Commit with a concise imperative message.
  • Prefer type(scope): summary when the change has an obvious type/scope; otherwise use a clear plain-English summary.
  1. Repeat until done.
  • After each commit, re-check git status -sb.
  • Continue until all intended changes are committed or intentionally left uncommitted.
  1. Report the result.
  • List the commit SHAs and messages in order.
  • Note any remaining staged/unstaged/untracked files.

Safety Rules

  • Avoid git add -A unless the entire remaining diff belongs in one commit.
  • Use partial staging when a file mixes multiple concerns.
  • Do not rewrite or discard user changes unless explicitly asked.
  • If grouping is ambiguous, ask before committing.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

assistant

무료

Meet or work with Assistant, the user's relaxed ongoing work support. Use when the user invokes Assistant, starts or resumes an Assistant chat, asks what they should know, wants proactive work awareness, asks for reply drafts, asks to keep an eye on work, or needs follow-up/check-in help. On first contact, start with exactly "Hi, I'm your assistant." then decide whether onboarding is brand new, partial, or already established.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-code

무료

Audit, de-slop, parameterize, modularize, or safely clean up AI-generated or AI-shaped backend/general code. Use for Python, TypeScript, or other implementation diffs that may contain duplicate helpers, fixture hacks, hard-coded test data, over-defensive control flow, broad exception wrappers, config-bag or boolean-mode soup, speculative scaffolding, hallucinated APIs/dependencies, local-idiom drift, brittle tests, or maintainability/safety/performance gaps after a feature, bugfix, prototype, or agent pass.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-frontend

무료

Audit AI-generated, AI-shaped, or AI-looking frontend code, UI screenshots, and design diffs. Use for prompts like "audit AI frontend", "de-slop UI", "componentize this screen", "parameterize this React/Tailwind/shadcn UI", "make it responsive/accessible", or "review design-system drift"; check component APIs, reusable props/data models, modular composition, shared primitives/tokens, responsive resilience, accessibility, copy quality, hard-coded fixture screens, one-off CSS piles, and generic cards/gradients/fonts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

audit-ai-writing

무료

Audit pasted chatbot output, AI-cleanup diffs, wiki drafts, Markdown/MDX/docs, and source-backed articles for generic AI fluff, LLM writing tells, weak audience model, lack of theory of mind, inflated significance, vague attribution, leaked tokens, placeholders, broken markup, fabricated or mismatched citations, and detector false positives. Use for requests like "AI writing audit", "check for AI slop", "find writing fluff", "does this sound like ChatGPT", "cleanup LLM tells", "make this less generic", "verify these citations", "detector flagged this", or text containing turn0search0, oaicite, oai_citation, contentReference, utm_source=chatgpt.com, malformed references, or wrong target-format markup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

gh-address-comments

무료

Help address review/issue comments on the open GitHub PR for the current branch using `oai_gh` or `gh`; verify auth first and prompt the user to authenticate if not logged in.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

gh-fix-ci

무료

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `oai_gh` or `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

jxnl/personal-monorepo-template5732026년 6월 23일 업데이트

jxnl의 스킬 모두 보기

이 스킬의 문제 신고