「commit」の検索結果

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

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

[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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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 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.

日本語の概要は準備中です。原文の説明を表示しています。

Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive skill for working with Azure DevOps REST API across all services including Boards (work items, queries, backlogs), Repos (Git, pull requests, commits), Pipelines (builds, releases, deployments), Test Plans, Artifacts, organizations, projects, security, extensions, and more. Use when implementing Azure DevOps integrations, automating DevOps workflows, or building applications that interact with Azure DevOps services.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub PR lifecycle: branch, commit, open, CI, merge.

日本語の概要は準備中です。原文の説明を表示しています。

Run quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.

日本語の概要は準備中です。原文の説明を表示しています。