'ownership' 검색 결과

Analyze git history to map contributors to security-sensitive files and identify ownership gaps. Estimate bus factor, a measure of dependence on few people, group files that change together, and export CSV or JSON for further analysis.

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

• Finding sensitive code with stale, concentrated ownership
• Checking reliance on one person for authentication code
• Comparing CODEOWNERS with contribution history

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

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

Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

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

Write, review, and debug Rust applications, including ownership and borrowing rules that govern memory use. Covers trait-based APIs, explicit error handling, asynchronous work with tokio, and tests with Cargo validation.

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

• Resolve ownership, borrowing, and lifetime errors
• Design APIs with traits
• Implement asynchronous tasks with tokio

Rust 코드를 작성·검토·개선하며 소유권, 오류 처리, 타입 설계와 동시성을 정리합니다. 안전성, 성능, 유지보수성을 고려한 구현을 돕습니다.

• Rust 소유권과 빌림 검토
• 오류 발생 시 중단되는 처리 개선
• Rust 앱의 타입과 모듈 설계

Coordinate employee offboarding across Okta, Google Workspace, Google Drive, and GitHub. Revoke access, reclaim licenses, and report checklist results, with human approval required for ownership transfers and no account deletion.

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

• Process newly flagged employee departures
• Offboard a specific employee on request
• Transfer document ownership with human approval

Task claiming and ownership tracking for parallel agent execution. Agents claim tasks from a shared queue with file ownership enforcement. Use during parallel execution phases when multiple agents work simultaneously.

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

Solid 2로 OpenClaw 화면을 구현하고 이전하며 검토와 테스트를 진행합니다. 상태 관리, Lit과의 공존, 대화상자 표시, 성능 확인을 다룹니다.

• Lit 화면을 Solid 2로 이전
• 상태 관리와 화면 갱신 검토
• 플러그인 화면과 대화상자 구현

Write and review Rust, C++, and C code with safer memory and resource management. Covers ownership, automatic cleanup tied to scope, and smart pointers to help prevent leaks, double frees, and access to freed memory.

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

• Design safer memory management in systems code
• Review cleanup of files, sockets, and memory
• Investigate memory leaks and access to freed memory

Organize feature development across multiple agents by dividing work, assigning one owner per file, and agreeing on interfaces before implementation. Provides strategies for shared files, branches, and integration so agents can build separate parts of the same system.

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

• Dividing a large feature among multiple agents
• Assigning file ownership to avoid conflicting edits
• Agreeing on APIs before parallel implementation

Plan Table v9 state ownership across the table, framework state, and external atoms that hold values. Covers initial values, update callbacks, and reset behavior, helping coordinate individual state sections without conflicting owners.

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

• Choosing where to manage pagination state
• Connecting external state to update callbacks
• Reviewing external atom ownership

Compares frameworks, libraries, and cloud providers using weighted criteria. Helps teams choose technologies with estimates of five-year total ownership costs, security assessments, community health indicators, and migration effort, risks, and timelines.

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

• Comparing frameworks for a new project
• Estimating five-year technology ownership costs
• Assessing migration effort and risks

Turn a meeting transcript into structured notes and one Linear ticket per action item. Assign owners from the discussion or the team’s ownership map, and flag unclear assignments in unassigned tickets for follow-up.

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

• Turn meeting transcripts into structured notes
• Create Linear tickets for meeting action items
• Assign tasks using the team’s ownership map

Write and review Rust code with clear ownership, reference lifetimes, asynchronous tasks, and explicit error handling. Use types to prevent invalid states, reduce unnecessary copying, and document the safety requirements of necessary unsafe operations.

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

• Resolving ownership and reference lifetime issues
• Building asynchronous tasks with tokio
• Preventing invalid states through type design

Examine how a job or business generates income through ownership, responsibility, and leverage—ways to expand output beyond personal working hours. Use the framework to consider equity, products, or content while setting limits on downside risk.

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

• Reviewing reliance on income tied to working hours
• Comparing salary and equity compensation
• Assessing whether a side business can scale

Refactor large SwiftUI screens into smaller views with clear inputs and state ownership. Organize actions, shared dependencies, and observable models while preserving existing layout and behavior, making the code easier to read and test.

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

• Split a large SwiftUI screen into smaller views
• Clarify state ownership and data flow
• Move business logic out of the view body

[omh] Rust ownership, lifetime, or unsafe trouble: prepare Rust changes with ownership, error, and API discipline, and escalate any unsafe, FFI, or lock-free change to the UB checklist. Use when the user says: rust, rust code, rust skill, rustlang, borrow checker, lifetime error, ownership error, trait bound.

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

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.

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

Diagnose and mitigate Salesforce data skew — ownership skew (single user owns >10,000 records) and parent-child skew (>10,000 children under one parent) — that cause sharing recalculation slowness, group membership lock errors, and record-level locking failures. Covers lookup skew and UNABLE_TO_LOCK_ROW, Defer Sharing Calculation (deferGroupMembership / deferSharingRules in Sharing.settings), ownership bucket groups, Controlled by Parent OWD, Bulk API serial vs parallel concurrency for skewed loads, and the documented load ordering for roles, groups and sharing rules. NOT for planning and batching a recalculation job — use data/sharing-recalculation-performance. NOT for designing the sharing model itself — use admin/sharing-and-visibility.

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

Ensure designs define data flow, state ownership, consistency boundaries, and cross-boundary writes to prevent drift and incidents.

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

Autonomous build-ship-verify loop that ends with code committed, deployed, and confirmed live. Triggers on: "$ownership", "execute X with ownership", "build this overnight", or any request for an autonomous product loop with no human checkpoints until production is verified. NOT for: one-off tasks, quick fixes, or supervised dev work (use devprocess for those).

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