Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Use this after an upgrade plan has a reviewed target.
Update the manifest and lockfile with the package manager. Make only the code or configuration edits required by the verified migration notes. Do not mix formatting, refactors, unrelated package bumps, or silent alert suppressions into the change.
Run the smallest relevant tests first, then the project checks required by its contribution guide. Inspect the resolved dependency tree and built artifact. For a security fix, rerun the scanner or version check that found it. Record commands, results, and anything you could not run.
State the old and new versions, reason, advisory or release-note sources, behaviour changed, files changed, test evidence, known risk, rollout check, and rollback. Mark it draft when approval or a check remains.
Never merge, deploy, bypass a failed check, or claim production is fixed. Hand the draft and evidence to the named reviewer.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ad variants that each test one idea, within platform limits and supported claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.