'maintenance' 검색 결과

Plan and evaluate free calculators, generators, or assessment tools for marketing. Compare ideas against audience needs, search demand, development effort, and maintenance, then define an initial version and a path toward your paid product.

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

• Comparing free tool ideas for attracting prospects
• Defining the first version of an ROI calculator
• Deciding when to request an email address

Design evaluation tasks that check whether agents actually complete work. Define requests, simulated user behavior, starting conditions, and verifiable success criteria, then plan difficulty levels, training-data leakage checks, and ongoing maintenance.

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

• Creating evaluation tasks for real business workflows
• Reviewing success criteria and verification logic
• Designing checks for evaluation data leakage into training

Delegate a feature, bug fix, or substantial code change and carry it through implementation, review, and verification. Start from a task description or issue link, with options for the workflow route and review depth.

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

• Delegating implementation of a new feature
• Fixing a bug described in an issue
• Choosing review depth for a substantial code change

Investigate Cherry Studio code to identify unused behavior, duplicated state, and unnecessary abstractions. Turn a few well-supported findings into cleanup proposals that document current consumers, removal scope, risks, and observable acceptance criteria.

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

• Finding unused code and unnecessary internal APIs
• Reviewing duplicated stores, caches, and events
• Assessing library replacements that reduce maintenance

Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.

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

• Create an OpenAPI specification from an existing API
• Write getting-started and authentication guides
• Prepare and test API request examples

Review CLAUDE.md files, which provide project instructions to Claude Code. Receive a scored quality report covering commands, structure, and outdated guidance, then approve focused edits that keep the instructions concise and useful.

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

• Auditing project instructions for Claude Code
• Updating outdated build and test commands
• Reviewing instructions across multiple packages

Assess software dependencies, build pipelines, and container images for security risks. Create a software component inventory, check vulnerabilities and license conflicts, verify artifact signatures, and prioritize fixes based on whether vulnerable code can actually be reached.

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

• Creating and auditing a software component inventory
• Prioritizing dependency vulnerabilities by actual exposure
• Auditing CI/CD pipelines and secret handling

Review code for security, performance, quality, and ease of maintenance. Get an overall assessment and prioritized findings with file locations, severity, explanations of impact, and example fixes to guide improvements or Pull Request reviews.

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

• Reviewing a Pull Request before merging
• Checking authentication and data exposure risks
• Finding inefficient queries and processing

Review code for security, performance, quality, and ease of maintenance. Receive an overall assessment and categorized findings, with file locations, severity, impact, and code examples for addressing critical issues.

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

• Reviewing a pull request
• Checking authentication and sensitive data handling
• Finding inefficient algorithms or database queries

Review code for security, performance, quality, and ease of maintenance. Receive an overall assessment and categorized findings, with file locations, severity, impact, and code examples for addressing critical issues.

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

• Reviewing a pull request
• Checking authentication and sensitive data handling
• Finding inefficient algorithms or database queries

Design reusable interface components in React, Vue, and Svelte. Organize how components fit together, define clear configuration options, and choose styling approaches while addressing accessibility, responsive layouts, and maintenance across component libraries or design systems.

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

• Build a reusable UI component library
• Standardize component options across a design system
• Refactor complex existing components

Investigate slow SQL using execution plans, which show how a database processes a query. Review indexes, filters, joins, and maintenance practices through PostgreSQL examples to identify bottlenecks and plan changes to queries or database structure.

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

• Investigating slow SQL queries
• Reviewing index choices and column order
• Reading EXPLAIN execution plans

Refactor Java methods by extracting related blocks into separate, clearly named methods. Assess method length and complexity, preserve existing functionality, and return complete Java 17 methods with brief comments explaining each newly extracted method.

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

• Split a long Java method into smaller methods
• Separate distinct operations within complex methods
• Name extracted logic to clarify its purpose

Plan and explain Lakehouse solutions in Microsoft Fabric, a place to manage tables and files together. Understand data organization, links to data without copying, access controls, and table maintenance options for designing and improving a solution.

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

• Writing an introduction to Fabric Lakehouse
• Planning how to organize tables and files
• Reviewing data links and access controls

Deploy a Software-Defined Perimeter that connects verified users to authorized applications. Configure single-packet authorization, mutual certificate authentication, access policies, and monitoring, then test whether unauthorized connections and access between applications are blocked.

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

• Building zero trust access to internal applications
• Hiding services from unauthenticated network scans
• Testing certificate authentication and access restrictions

Set up decoy credentials, storage, and secrets across AWS, Azure, and GCP to detect suspicious access. Connect audit logs to security alerts, verify detection, and document permissions, resource inventories, and maintenance plans.

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

• Detecting use of leaked cloud credentials
• Monitoring suspicious access to decoy storage and secrets
• Extending on-premises deception coverage to cloud environments

Document major technical decisions with their context, alternatives, reasoning, and consequences. The skill provides Architecture Decision Record templates and maintenance practices so teams can review past choices, track replacements, and explain decisions to new members.

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

• Recording reasons for technology choices
• Comparing design options and trade-offs
• Explaining past decisions to new team members

Set up a lasting wiki knowledge base for a NanoClaw group. The skill helps define its topic, organize source files and wiki pages, and establish workflows for adding material, answering questions, and checking the wiki.

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

• Build a wiki around a research topic
• Turn collected documents into connected knowledge
• Define wiki maintenance rules with an agent

Plan tests for APIs, interfaces, data pipelines, and infrastructure. Choose suitable test types, prioritize critical behavior, and produce a plan with coverage targets and example cases while balancing thoroughness, execution speed, and maintenance effort.

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

• Planning tests for a new feature
• Finding gaps in existing test coverage
• Choosing test types for APIs and interfaces

Navigate the Composio SDK monorepo, a repository containing multiple packages, and follow its shared development rules. Use it to decide where changes belong, handle generated files and release metadata, and prepare branches and pull requests.

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

• Planning changes across multiple packages
• Deciding where code belongs
• Checking generated-file and release metadata rules

Review open GitHub issues, proposals, and pull requests to identify useful maintainer work. Get ranked candidates with evidence, dependencies, and validation needs, then begin work only on an item you explicitly select.

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

• Choose the next maintenance task
• Prioritize a backlog for the available work window
• Find pull requests that need review

Assess GitHub issues and pull requests by checking demonstrated user needs, existing alternatives, compatibility, and maintenance costs. Produce an evidence-based maintainer recommendation through code and document inspection, without running tests or examples.

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

• Deciding whether a pull request merits merging
• Checking whether existing features already solve an issue
• Comparing competing fixes for the same problem

Maintain an application's supported language models by checking provider availability, adding models, and keeping documentation, live tests, and model-specific request settings aligned. It also checks provider model identifiers and candidates for the recommended list.

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

• Add support for a specific language model
• Check whether listed models are still available
• Update provider model identifiers

Scan repository documentation, tests, and code for small, well-supported problems, then apply minimal fixes on one branch. Verify each fix before committing it separately, and record larger findings for reporting.

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

• Running scheduled repository maintenance
• Finding small issues in documentation, tests, and code
• Collecting separately verified fixes on one branch