'commit' 검색 결과

Quick repo-hygiene and consistency checks before committing.

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

Handle an explicit Git intent such as branch/worktree setup, commit organization, history archaeology, conflict resolution, PR preparation, or versioning; do not trigger as a process skill for every code or file change.

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

Detects leaked API keys, tokens, passwords, and credentials in code with pre-commit hooks, CI checks, scanning rules, and remediation procedures. Use for "secret scanning", "credential detection", "API key leaks", or "secret management".

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

Generates changelogs and release notes from git commits, PR titles, and issue references. Organizes changes by impact type (breaking, features, fixes, improvements), formats according to Keep a Changelog standard, and provides version tagging and semantic versioning suggestions. Use when users request "create changelog", "write release notes", "document version changes", or "prepare release".

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

Use when a Spark branch or pull request needs final diff hygiene, validation selection, commit scope, remote topology, and readiness checked before publication.

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

Use when automating research session rituals in Claude Code with hooks, such as session-start context injection, daily research logging, session-end persistence, or pre-commit guards that block secrets and unverified citations.

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

Use when an ethics committee or IRB application involves AI anywhere in the pipeline, when KVKK, GDPR, or EU AI Act duties must be mapped to a study, or when consent and disclosure language about AI use needs drafting before submission.

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

Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder), continuous monitoring (new subdomain alerts, JS change detection, GitHub commit watch). Use when starting recon on any web2 target or when asked about asset discovery, subdomain enum, or attack surface mapping.

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

Comprehensive offensive methodology for software supply chain attacks covering the full kill chain from reconnaissance through exploitation. Addresses dependency confusion across npm, PyPI, and NuGet ecosystems where internal registry override allows an attacker to inject malicious packages that shadow private dependencies. Covers typosquatting techniques for popular packages, compromised package injection via maintainer account takeover or social engineering, and build system attacks through Makefile injection, setup.py install hooks, and npm postinstall scripts. Extends into CI/CD artifact tampering where build outputs are replaced or modified in transit, code signing abuse through stolen or self-signed certificates, upstream repository compromise via commit injection or force-push to trusted repos, and container image supply chain attacks including base image trojaning and registry confusion. Maps to MITRE ATT&CK T1195.001 (Supply Chain Compromise: Compromise Software Dependencies and Development Tools...

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

Review all uncommitted changes in the current repo and produce a structured code review report.

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

Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.

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

Requires OFOX_API_KEY — create one at https://app.ofox.ai. Generate cheap vertical 9:16 drafts in one priced batch, pick a winner off the contact sheet, then re-render only that one. The cheap tier is the point — several times cheaper per second, so a whole set can cost less than one flagship clip. Use when a user wants Shorts/Reels/TikTok raw material rather than one finished video, e.g. "give me 5 vertical clips to choose from", "a few Reels drafts for this product", "some cheap options before we commit", or "batch me some 9:16 takes". Do not use when one finished clip is wanted — go straight to the scenario skill (seedance-ad-creative, ugc-ads, seedance-short-drama, seedance-product-video), which is also where this skill gets the prompt it drafts.

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

Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.

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

Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then guides read-only inspection, failure classification, smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md.

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

Use when the user requests React Doctor or a React code-health audit, or when a concrete React diagnostic question would benefit from its scan. Not a default step after React changes or before committing.

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