'before' 검색 결과

작업 완료나 오류 수정 성공을 보고하기 전에 테스트와 빌드를 실행하고 결과를 확인합니다. 커밋이나 풀 리퀘스트 생성 전에도 실제 출력을 근거로 현재 상태를 전달합니다.

• 완료 보고 전 결과 확인
• 오류 수정 여부 검증
• 커밋이나 풀 리퀘스트 생성 전 검증

Verify development results before reporting success or preparing commits and pull requests. Run checks that support each claim, inspect their actual output, and report remaining gaps instead of relying on assumptions or another agent’s success message.

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

• Checking evidence before reporting a bug as fixed
• Confirming test and build results before a commit
• Verifying that a regression test detects the bug

Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.

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

• Checking results before reporting completion
• Confirming that a bug fix resolves the original problem
• Verifying work before a commit or pull request

새 기능을 구현하기 전에 기존 코드, npm과 PyPI 패키지, MCP servers 등을 조사합니다. 후보를 비교해 채택, 확장, 조합 또는 직접 개발할지 판단하도록 돕습니다.

• 기능 추가 전에 기존 해결책 조사
• 의존성 추가 전 패키지 비교
• 외부 서비스 연동 도구 조사

Check text, code, and configuration files for personal information and secrets before committing, logging, storing, or sending them. Identify categorized findings, flag their locations, and suggest redaction to hide sensitive details.

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

• Check code for personal information before committing
• Inspect logs before saving them
• Check model responses before sending them

Review bulk deletions before they happen by showing affected data, recovery options, and alternatives. The skill asks for explicit user consent and records confirmed deletions, covering files and gbrain data through agent procedures.

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

• Reviewing files before a bulk cleanup
• Checking recovery options before deleting knowledge pages
• Confirming impact before dropping database tables

Create and review Mastra tests that reproduce user-visible failures through public APIs, real network requests, and actual storage. Verify that tests fail before a fix and cover the different execution paths affected by the bug.

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

• Reproduce a reported bug before fixing it
• Review tests that rely heavily on mocked dependencies
• Check regression coverage across engines and adapters

Establish repeatable performance measurements for MSBuild and .NET builds before optimizing. Compare clean-output, changed-source, and unchanged builds, record timing ranges, and assess output layouts, dependency references, and parallel build options against the measured baseline.

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

• Measure slow builds before choosing an optimization
• Compare build times before and after changes
• Check rebuild behavior after a small source edit

Identify the checks required for changed files, run tests, and review applicable project rules. Get a table of passed, failed, and skipped checks with evidence, helping you verify changes before handoff or pushing code.

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

• Checking changes before reporting work complete
• Reviewing required checks before pushing code
• Finding missing tests or documentation updates

Identify one to three important decisions before starting a build. Based on the user's idea, this skill presents concise options and an initial recommendation for each, then waits for answers before work proceeds.

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

• Clarifying important decisions before implementation
• Deciding whether a solution needs to be reusable
• Choosing between a short script and a separate module

공개 전 글이나 코드를 두 독립 에이전트가 같은 기준으로 심사합니다. 모두 통과할 때까지 수정과 재심사를 반복하고, 반복 한도에 도달하면 미해결 문제를 사람에게 넘깁니다.

• 공개 전 글의 사실관계 확인
• 고객용 글과 브랜드 규칙 대조
• 운영 환경 배포 전 독립 심사 추가

라우터와 스위치에 설정을 적용하기 전에 위험한 명령, IP 주소 중복, 서브넷 중첩, 정의되지 않은 참조와 관리 접속 문제를 점검합니다.

• 유지보수 전 설정을 검토합니다
• 템플릿으로 생성한 설정을 감사합니다
• IP 중복과 네트워크 범위를 확인합니다

구현된 UI의 시각적 문제를 점검하고 코드를 수정합니다. 변경을 작은 단위로 커밋하고 수정 전후 스크린샷을 제공하여 출시 전 화면을 확인할 수 있습니다.

• 출시 전 UI 외관 점검
• 시각적 점검 결과에 따른 코드 수정
• UI 수정 전후 스크린샷 비교

Research a coding task before implementation and turn it into a detailed work plan with decisions, dependencies, and verification steps. The plan is written after approval, while code changes remain a separate workflow.

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

• Planning a large change before implementation
• Turning a vague request into concrete tasks
• Preparing a plan for another agent to execute

Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.

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

• Plan implementation steps before changing code
• Design a phased migration with rollback steps
• Break work into separate commits or pull requests

Retrieve relevant Hindsight memories before planning or answering a request. Searches the agent’s own and shared memory stores, plus other relevant stores when needed, to bring past decisions, user preferences, and project context into the task.

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

• Checking past decisions before planning work
• Answering with previously recorded user preferences
• Finding context saved by other Bots or AI tools

Review a product or major feature before development starts. Assess demand, revenue, repeat use, trust, and user reach, then identify the riskiest assumption, a small validation step, and work to delay.

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

• Check demand and revenue assumptions before building an MVP
• Review positioning before creating a landing page
• Assess adoption risk for a major feature

Plan Codewhale changes by locating the existing implementation and its callers, defining one reviewable change, and choosing verification before editing. Use it for features, upgrades, and refactoring to avoid duplicate implementations and unfinished migrations.

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

• Locate existing code before adding a feature
• Define a reviewable scope for refactoring
• Choose checks before implementation

Research customer questions using available internal documents, account history, support records, and public sources. Produce a brief with an answer, source references, confidence level, unresolved questions, and recommended next steps before drafting a customer response.

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

• Check product capabilities before answering a customer
• Find previous bug reports and known workarounds
• Review what a specific customer was told before

Evaluate a proposed software change before implementation. It examines project files and official sources, compares options and trade-offs, and builds a concrete plan covering affected systems, effort, risks, and unresolved questions for the user's approval.

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

• Discuss a major change before implementation
• Compare migration or configuration options
• Estimate affected files and implementation effort

Examine a plan by imagining it has failed twelve months later. Identify weak assumptions, linked dependencies, and commitments that are hard to reverse, then outline validation steps and criteria for continuing, changing direction, or stopping.

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

• Reviewing a plan before committing major resources
• Checking assumptions before a board or investor presentation
• Examining plans that receive only positive feedback

Load company background for executive advisor sessions, check whether it is outdated or incomplete, and propose updates learned during conversations. Apply rules for excluding sensitive details and anonymizing permitted information before external searches or API calls.

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

• Loading company background before an executive advisor session
• Checking outdated or incomplete company information
• Proposing context updates from new conversation details

Manage which n8n instance an MCP session targets when working across production, staging, teams, or clients. Guides instance switching, checks before credential changes, and recovery from unexpected missing data or ambiguous credential writes.

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

• Switching between production and staging
• Checking the target before credential changes
• Investigating unexpected missing data

Use Memori Cloud from Claude Code to consult stored preferences, decisions, and project history before substantive work, then save the exchange afterward. Recall can span sessions and use filters for dates and information types.

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

• Check previous decisions before coding
• Recall preferences and project requirements
• Review progress after time away