Agent Skills: Fetch Team Context Skill

Fetch Semicolon team standards from docs wiki. Use when (1) providing workflow or process advice, (2) recommending DevOps strategies, (3) referencing team conventions for decision-making, (4) checking team standards compliance.

UncategorizedID: semicolon-devteam/semo/fetch-team-context

Install this agent skill to your local

pnpm dlx add-skill https://github.com/semicolon-devteam/semo/tree/HEAD/semo-system/semo-skills/fetch-team-context

Skill Files

Browse the full folder contents for fetch-team-context.

Download Skill

Loading file tree…

semo-system/semo-skills/fetch-team-context/SKILL.md

Skill Metadata

Name
fetch-team-context
Description
Fetch Semicolon team standards from docs wiki. Use when (1) providing workflow or process advice, (2) recommending DevOps strategies, (3) referencing team conventions for decision-making, (4) checking team standards compliance.

πŸ”” μ‹œμŠ€ν…œ λ©”μ‹œμ§€: 이 Skill이 호좜되면 [SEMO] Skill: fetch-team-context 호좜 - {ν† ν”½} μ‹œμŠ€ν…œ λ©”μ‹œμ§€λ₯Ό 첫 쀄에 좜λ ₯ν•˜μ„Έμš”.

Fetch Team Context Skill

Purpose: Retrieve Semicolon team standards, processes, and conventions from docs wiki for informed decision-making

When to Use

Agents should invoke this skill when:

  • Providing workflow or process advice
  • Recommending DevOps strategies
  • Checking team conventions before suggesting changes
  • Validating recommendations against team standards

Quick Start

1. Identify Required Context

| Topic | Wiki Page | |-------|-----------| | Git & Commits | Team Codex | | Workflow | Collaboration Process | | Architecture | Development Philosophy | | Estimation | Estimation Guide |

2. Fetch via GitHub API

# List all wiki pages
gh api repos/semicolon-devteam/docs/contents | jq '.[].name'

# Web fetch fallback
web_fetch({ url: "https://github.com/semicolon-devteam/docs/wiki/Team-Codex" });

3. Extract Key Information

Parse fetched content for:

  • Rules: MUST, SHOULD, MUST NOT patterns
  • Conventions: Naming, formatting, structure
  • Processes: Step-by-step workflows
  • Examples: Code snippets, command examples

Usage

// Fetch specific context
skill: fetchTeamContext({ topic: "git-commits" });

// Fetch multiple contexts
skill: fetchTeamContext({ topics: ["workflow", "code-quality"] });

Critical Rules

  1. docs wiki is Source of Truth: Always prefer wiki over cached data
  2. Explicit Over Implicit: If wiki doesn't specify, don't assume
  3. Version Awareness: Note if wiki content seems outdated
  4. Fallback Gracefully: Use quick reference if wiki unavailable
  5. Attribution: Always cite source URL in responses
  6. λ¬Έμ„œ μœ νš¨μ„± 검증 ν•„μˆ˜: 404 응닡이면 λ°˜λ“œμ‹œ μ‚¬μš©μžμ—κ²Œ μ•Œλ¦Ό

Dependencies

  • gh api - GitHub API access
  • web_fetch - Web content retrieval (fallback)
  • docs wiki - Source of truth

Related Skills

  • check-team-codex - Uses this for code quality rules
  • create-issues - Uses this for issue conventions
  • implement - Uses this for development workflow

References

For detailed documentation, see: