Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
**UTILITY SKILL** - Explain code snippets, functions, and algorithms in plain language. USE FOR: explain code, what does this code do, break down this function, help me understand this, walk through this algorithm, clarify this logic, explain this snippet, describe what happens here. DO NOT USE FOR: writing new code (use code generation), fixing bugs (use debugging), refactoring (use refactoring skills), code review with action items. INVOKES: file reading tools to access code, language detection for tailored explanations. FOR SINGLE OPERATIONS: If the user just needs to see file contents, use file reading tools directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
A skill that explains code snippets in clear, educational language. Helps developers understand unfamiliar code, algorithms, and programming patterns.
Use this skill immediately when the user asks to:
Key Indicators:
Do NOT use when:
| Property | Value |
|---|---|
| Input | Code snippet + optional language hint |
| Output | Plain language explanation |
| Best for | Learning, onboarding, code comprehension |
A good code explanation should include:
| Language | Focus On |
|---|---|
| Python | List comprehensions, decorators, generators |
| JavaScript | Async/await, closures, callbacks |
| SQL | JOINs, subqueries, aggregations |
| Java | OOP patterns, generics, streams |
User prompt:
Explain this code:
```python
def factorial(n):
if n <= 1:
return 1
return n * factorial(n - 1)
Good response:
This is a recursive function that calculates the factorial of a number.
Overview: It multiplies a number by all positive integers less than it (e.g., 5! = 5 × 4 × 3 × 2 × 1 = 120).
Step by step:
- Base case (
if n <= 1): If n is 0 or 1, return 1 (since 0! and 1! both equal 1)- Recursive case: Otherwise, multiply n by factorial(n-1)
Example:
factorial(4)→ 4 × factorial(3) → 4 × 3 × factorial(2) → 4 × 3 × 2 × factorial(1) → 4 × 3 × 2 × 1 = 24
User prompt:
What does this code do?
```javascript
async function fetchUserData(userId) {
try {
const response = await fetch(`/api/users/${userId}`);
if (!response.ok) throw new Error('User not found');
return await response.json();
} catch (error) {
console.error('Failed:', error);
return null;
}
}
Good response:
This is an async function that fetches user data from an API.
Overview: It makes an HTTP request to get a user's data, handles errors gracefully, and returns the result as JSON.
Step by step:
async function- Declares this function will use await for promisesawait fetch(...)- Makes HTTP GET request, waits for responseif (!response.ok)- Checks if request succeeded (status 200-299)await response.json()- Parses response body as JSONcatchblock - If anything fails, logs error and returns nullKey pattern: This is the standard async/await pattern for API calls with error handling.
If the user provides:
This skill works well with:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare and publish a new version of the waza azd extension. USE FOR: "publish extension", "release new version", "bump version", "prepare release", "update changelog", "azd publish", "new release", "version bump", "cut a release". DO NOT USE FOR: running evals (use waza), writing skills (use skill-authoring), CI/CD pipeline changes (edit workflow files directly).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explains code snippets in plain English, breaking down what the code does step by step. Perfect for learning, code reviews, or documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The complete two-phase Init Mode protocol the Squad coordinator runs when no team exists yet in the current repo. Phase 1 = propose the team (no files created, wait for user confirm). Phase 2 = create .squad/ scaffolding, casting state, .gitattributes for merge drivers, and the always-on built-ins (Scribe, Ralph, Rai, Fact Checker). Loaded on demand when the coordinator detects no .squad/team.md exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Selecting WHO handles work is the Routing table; selecting HOW they handle it (Direct, Lightweight, Standard, Full) is Response Mode. This skill contains the complete decision table, exemplar prompts for each mode, the Lightweight spawn template, and the upgrade rules. Squad coordinator loads this on demand once routing has identified the agent — to pick the right ceremony level for the task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.