Results for “update”

Locate CCSBot::Update in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSBot::Update" (symbol CCSBot_Update). 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: CCSBot_Update, CCSBot::Update

The English summary is being prepared. Showing the original description.

Locate CCSBot::UpdateLookAngles in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSBot::UpdateLookAngles" (symbol CCSBot_UpdateLookAngles). 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: CCSBot_UpdateLookAngles, CCSBot::UpdateLookAngles

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Periodic dependency update run. Reads what the package manager says is outdated, upgrades what is safe, applies the code changes the new versions need, verifies, and opens one reviewable PR. Supports a read-only dry run that reports what it would do. Use when the user says "dependency update", "/dependency-update", "update deps", "dry run the dep update", or when a scheduled cloud routine fires.

The English summary is being prepared. Showing the original description.

Update an existing local or remote OpenClaw Gateway through its established deployment workflow. Identify the responsible updater, follow restart and recovery procedures, and verify that the intended version is serving and configured connections work.

• Updating a local OpenClaw Gateway
• Choosing the update workflow for a managed server
• Checking session recovery after a restart

Coordinate updates to an operator-configured Team server through its designated Night Watch owner. Use the existing deployment controller’s validation, recovery, and acceptance records to follow the requested update through completion.

• Updating a Team server to official main
• Following up on failed or deferred updates
• Coordinating database migration and recovery

Update a live OpenClaw checkout on macOS, then verify its Gateway and local app. Investigate automated check failures, repair them through focused pull requests, and run release validation without publishing a release.

• Updating a live OpenClaw installation on macOS
• Verifying Gateway and app behavior after updates
• Repairing automated checks for the current main commit

Check a pull request’s title and description against its commits and code changes. Identify missing major changes or outdated claims, propose accurate wording, and apply agreed updates while following the repository’s existing template.

• Check whether a pull request description matches the implementation
• Add major changes missing from a pull request summary
• Update an outdated pull request title

Audit article update dates across the visible page, HTTP response headers, and structured data that describes the article to search engines. Align these signals with substantive content changes and review how the CMS or build process updates them.

• Auditing update dates on articles and blog posts
• Reviewing CMS rules for updating modification dates
• Checking timestamps applied during static site deployments

Bring a Remotion branch up to date with the official main branch while preserving local changes and published history. Handle temporary change storage, merges, conflicts, validation, and a normal push when requested.

• Merge the latest main into a feature branch
• Fast-forward a local main branch
• Update a pull request branch while preserving published history

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Update figures throughout an existing presentation while preserving its formatting. Find equivalent values across text, tables, and chart data, present a change list for approval, and flag related growth rates or percentages that may need recalculation.

• Updating a presentation with quarterly results
• Refreshing figures in peer comparison slides
• Replacing values using an Excel update sheet

Create and update GitHub issues for bugs, feature requests, and tasks. Organize owners, labels, dates, and priorities, connect related work, and track dependencies and project progress through MCP tools and the GitHub API.

• File bug reports and feature requests
• Update issue owners, dates, and priorities
• Organize parent tasks, subtasks, and dependencies

Build a repeatable process for Microsoft monthly security updates, from reviewing advisories and ranking vulnerabilities to testing, staged deployment, and verification. Helps teams set response deadlines based on risk and report remaining unpatched systems.

• Establishing a monthly Microsoft security update workflow
• Prioritizing vulnerabilities by exploitation risk
• Planning pilot and production deployment stages

Invite several people to an existing Google Calendar event using a list of email addresses. The workflow retrieves the event, updates its attendees, sends update notifications, and checks the event again to verify the changes.

• Inviting several colleagues to an existing meeting
• Adding attendees and sending event update notifications
• Checking the attendee list after an update

Find a sales tracking spreadsheet in Google Sheets, review its current entries, and append a deal update with the date, company, status, amount, quarter, and owner.

• Record a deal update after sending a proposal
• Add a deal's amount, quarter, and owner
• Review existing entries before logging an update

Read and update Google Docs through gws commands. Create blank documents, retrieve the latest version, append text, or apply multiple updates together, using command help and schema information to check the required inputs.

• Retrieving the latest version of a Google Docs document
• Creating a blank document with a chosen title
• Appending text to an existing document

Keep gbrain current by checking available updates, summarizing release changes, and applying or deferring upgrades according to configured preferences. Migration instructions take priority when a release requires an operator to supervise the update.

• Check whether gbrain has an available update
• Review release changes before upgrading
• Defer update reminders during ongoing work

Extract figures and fields from emails, websites, and APIs into source-linked tracking tables. Configurable recipes guide collection, preserve original material, and check duplicates for records such as investor updates, expenses, and company metrics.

• Track financial metrics from investor update emails
• Collect expenses from receipt emails
• Maintain a table of company updates

Turn recent work or rough notes into a concise daily standup update organized by yesterday, today, and blockers. Connected tools can supply commits, pull requests, ticket changes, and relevant discussions to help assemble the report.

• Preparing a concise daily standup update
• Turning rough work notes into a shareable report
• Summarizing commits, pull requests, and ticket changes

Review local code changes with git diff and update the matching pages under docs/. Keep commands, settings, examples, and navigation aligned with current behavior so readers can understand the changes without reading the code.

• Documenting uncommitted feature changes
• Updating setup instructions after a refactor
• Replacing outdated commands and configuration examples

Structure board presentations and investor updates using financial, sales, product, and people perspectives. Turn supplied metrics into a coherent account of progress, explain missed targets, and make decisions and requests explicit, with placeholders for missing figures.

• Preparing a quarterly board presentation
• Drafting a monthly investor update
• Structuring a fundraising narrative

Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.

• Bring the latest main changes into a feature branch
• Resolve conflicts while preserving both changes’ intent
• Sync remote feature branch updates before merging

Collect and update 68 US economic and social indicators, then summarize trends over ten, five, two, and one years. Produce a report covering relationships between indicators, unusual patterns, and topics that warrant further research.

• Refreshing US economic and social indicators
• Comparing short- and long-term economic trends
• Examining relationships across prices, jobs, and housing