'commit' 검색 결과

Agentic and machine-to-machine payments on Stellar. Covers x402 (HTTP 402 paid APIs via OZ Channels facilitator, fee-sponsored clients) and MPP (Machine Payments Protocol) in both Charge mode (per-request SAC) and Channel mode (off-chain commits, high-frequency). Defaults to USDC (SEP-41 SAC) on `stellar:testnet`/`stellar:pubnet` (CAIP-2). Use when selling a paid API to AI agents, building an x402 client, or designing a payment-channel architecture for high-frequency agent traffic.

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

Promote QA → production by opening a PR from peterdrier/Humans:main to nobodies-collective/Humans:main with a properly-qualified commit summary. Use when the user says "PR to production", "promote to prod", "PR from origin to upstream", "prod PR", or any variation of pushing batched fork changes upstream. Always use this skill for the two-remote promotion flow even if the user doesn't say "prod" explicitly.

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

Adversarial triage of open review findings on a PR. Every finding (Codex, Claude bot, Gemini) is a hostile hypothesis to REFUTE — fix only what is proven real, reachable, in the PR's scope, and above the round's severity bar. The bar rises every review round. Everything else is declined or filed as an issue. Use for 'fix the PR findings', '/fix', '/fix 123', or before any fix commit in a review loop.

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

Autonomous tech-debt reduction workflow for the Humans repository. Use when the user wants Codex to improve high-value code quality issues in a dedicated git worktree branched from origin/main, commit each improvement separately, push progress, and continue until diminishing returns.

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

Run multiple Reforge-guided section-refactor lanes in parallel, each in its own worktree/branch off origin/main, with a score-blind adversarial review panel gating every commit, one draft PR per section. Use when the user wants to reduce Reforge surface/internal score across several sections at once via architecturally-correct deletions (dead surface, entity-leak removal, cross-section consumers moved onto the public contract) — not by relocation, parameter bags, or accessibility-dodging. Wraps the per-lane process in .codex/skills/humans-refactor. Triggers: 'refactor swarm', 'parallel section refactors', 'run reforge refactor on Users/Tickets/...', 'burn down surface score across sections'. Has an intensity dial (light|standard|deep) and a workflow|solo execution mode to trade token burn against autonomy per unit of output.

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

Autonomous bug-hunt workflow for the Humans repository. Use when the user wants Codex to scan for real bugs, work in a dedicated git worktree branched from origin/main, commit each fix separately, push progress, and continue until diminishing returns.

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

Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.

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

Why expensive, wasteful, effortful, or self-deprecating actions build trust and desire — Rory Sutherland on signalling. Use when the problem is credibility or desirability rather than meaning: the user asks 'why don't people trust us', 'how do we look more credible/committed/premium', 'is our guarantee/warranty worth it', 'should we spend on brand advertising', 'how do we justify a higher price', or wonders why a cheaper-looking competitor wins. Covers costly signals (advertising spend, guarantees, over-delivery), price-as-quality-signal (Veblen goods), and the Pratfall Effect (admitting a real flaw to gain trust). Inspired by Rory Sutherland's *Alchemy*. Routed to from psycho-logic. 日本語の相談（「信頼されない」「安心してもらえない」「強気な価格で売りたい」「広告費に意味はある？」）にも使う。中文咨询（“不被信任”“想以高价出售”“广告费有意义吗？”）也适用。

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

Gitの変更をステージしてコミットする。「コミットして」「コミットしたい」「変更をコミット」といったリクエストで使用。差分を分析し、whatとwhyを含む適切なコミットメッセージを自動生成する。

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

Create an aggregated Epic PR from a `cc-epic-<Issue number>` branch to the default branch. Takes the Epic Issue number as argument, assumes sub-PRs have already been merged into the epic branch, and automatically generates the PR title and description from the commit log against the base branch (including sub-PR / sub-Issue references). The PR is posted via `gh pr create` with no label and `Closes #<Epic Issue>`.

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

Gate a build on browser fingerprint regressions with liarjs - save a baseline scan as JSON, diff later runs against it, and fail the job when the consistency score falls below a floor. Use when asked to add a fingerprint or headless-detection check to GitHub Actions, GitLab CI or another pipeline, to catch a regression in a Chromium build or scraping harness before it ships, or to track how a fingerprint score changes across commits.

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

Use when job costing a construction or contracting job: committed against actual cost, labour, plant, subcontract and materials allocation, margin by contract, variance to budget, and the cost-to-date and cost-to-complete figures the WIP calculation consumes.

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

Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

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

Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.

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

Route agent work through AccInt's MCP memory loop: retrieve prior outcomes, resolve frames, and close commitments with evidence.

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

Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.

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

Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.

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

Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"

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

Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install tools in docker'. Does: Interactively sets up Dockerfile.user and docker-compose.override.yml so users can add personal tools to their Docker environment without affecting maintainer files or committing user-specific config to git.

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

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

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

Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).

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

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

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