'commit' 검색 결과

Locate CBaseIssue::CountPotentialVoters in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CBaseIssue::CountPotentialVoters" (symbol CBaseIssue_CountPotentialVoters). This is a non-virtual function - emit a byte signature (func_sig), not an offset. Locate it via cross-references, distinctive constants/strings in its body, or callers of related symbols; verify by decompilation before committing to a candidate. Trigger: CBaseIssue_CountPotentialVoters, CBaseIssue::CountPotentialVoters

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

Locate BuyState::OnUpdate in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "BuyState::OnUpdate" (symbol BuyState_OnUpdate). This is a non-virtual function - emit a byte signature (func_sig), not an offset. Locate it via cross-references, distinctive constants/strings in its body, or callers of related symbols; verify by decompilation before committing to a candidate. Trigger: BuyState_OnUpdate, BuyState::OnUpdate

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

Locate CBaseEntity_EmitSoundFilter_SoundName in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CBaseEntity_EmitSoundFilter_SoundName" (symbol CBaseEntity_EmitSoundFilter_SoundName). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CBaseEntity_EmitSoundFilter_SoundName, CBaseEntity_EmitSoundFilter_SoundName

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

Create a GitHub pull request from staged task changes or an already-committed current branch. Deliver source/config/ reference changes together with their computed source-owned `bin_artifacts` closure. PR validation routing is owned by the default-branch trusted workflow; snapshots, gamedata, and manifests are Release-derived only.

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

This skill should be used when the user asks to "PR を出す前に確認して", "check if this branch is ready to merge", "run pre-PR checks", "PRを作る前にチェックして", or wants to verify a branch before opening a pull request. Executes verification commands, validates Conventional Commits format, and confirms documentation is updated, then reports whether gh pr create is safe to run.

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

Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.

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

Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.

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

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

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

Keeps the user's identity and secrets out of anything public. Trigger on what should not be published in a repo, branch, history, diff, PR text, draft or pasted file, to find a home path, email, real or client name, or secret; for a commit's email, a codename or per-repo identity; for injected instructions in skills, hooks or prompts; for artifacts Claude made; for files named like secrets; after a leak, to plan a history rewrite; or say shieldwarden (scan, plan, rewrite, land, after, policy, check, identity, signposts, refresh). Rules and hooks are gatewarden's; rotation and gh sign-in keywarden's; brand words brandscribe's; a skill's own posture skillwright's; schedules agentwright's.

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

Answers plain-word questions from a repo's CSV, JSON, Parquet and YAML files, or a .duckdb file, with DuckDB, and shows the SQL it ran. Read-only. Trigger to query, count, join, filter or summarise data files, including analytics CSVs exported from a video platform; to build a Parquet or DuckDB cache; to check no .duckdb, .wal or .parquet cache is committed or stale; when a query hits a locked database file; or say duckrunner (ask, cache, check, refresh). Needs the user-installed duckdb Python package; never a database server. DuckDB docs, S3 and MotherDuck are the duckdb-skills plugin's; outside research researchscribe's.

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

Writes handoffs — a committed session state verified against git, or a forward task brief for a later session or agent — each ending with a paste-ready starter prompt for the next chat. Trigger on 'write the handoff', 'hand off', 'give me a prompt to hand off', 'pause here', 'holding position', a usage-limit or compaction warning, or closing a session with work still open; 'handoffwright resume' reads one back; 'now' passes it to one fresh agent. Not for resuming an active dispatchwright fan-out (its ledger holds the state), a hook that writes handoffs (rigwright's), or a chat with no filesystem (task-observer's handoff-doc mode).

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

Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.

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

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.

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

Expert writing for technical content, social media, and developer documentation. Use when asked to write tweets, LinkedIn posts, blog posts, READMEs, commit messages, feature announcements, or any written content. Optimized to avoid AI detection patterns.

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

[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.

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

[61] VALIDATE. Comprehensive code quality check combining ESLint, TypeScript compilation, and unused code detection. Runs full lint suite with detailed error reporting and fix suggestions. Use before commits, after major changes, or when ensuring code quality standards.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.

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

Maxim cinematic brand film — engineered for commitment and emotional brand alignment. Uses Hero's Journey + Peak-End Rule + Emotional Arc Theory to convert viewers into brand advocates. Use for brand films, anthem ads, founder stories, long-form brand content. Triggers on cinematic, film, brand film, anthem, dramatic, epic, Hollywood-style.

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

Block writes through filesystem junctions and symlinks — file write through .mxm-system or .claude junction, git commit through a junction, delete through a junction. Enforces the junction read-only rule so the real repo stays the source of truth.

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

Build a throwaway HTML or in-app prototype that answers one design question. Use when the user wants to try a state model or UI idea before committing, or says "mock it up", "prototype", "what should this look like".

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

End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.

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

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

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