Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트
무료GitHub에 공개
debugging
Systematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous results
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기포함된 파일(1)
- SKILL.md2.5 KB
SKILL.md(원문)
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Debugging
Purpose
Systematically diagnose and resolve bugs, failures, or unexpected behavior in Genesis or its dependencies.
When to Use
- A test fails unexpectedly.
- Runtime error or unexpected behavior is reported.
- An awareness tick or reflection produces anomalous results.
- Obstacle resolution escalates a technical issue.
Workflow
- Reproduce — Confirm the issue. Get the exact error, stack trace, or unexpected output. Define "expected vs. actual."
- Isolate — Narrow the scope. Which module? Which function? Which input triggers it? Use binary search on the call chain.
- Hypothesize — Form 2-3 candidate explanations. Rank by likelihood.
- Test hypotheses — Write a minimal test or add logging to confirm/deny each hypothesis. Start with the most likely.
- Fix — Apply the minimal correct fix. Do not fix adjacent issues in the same change.
- Verify — Run the failing test. Run the full test suite. Confirm no regressions.
- Document — Record the root cause and fix as an observation. Update procedures if the bug class is recurring.
Output Format
issue: <one-line description>
date: <YYYY-MM-DD>
root_cause: <what actually went wrong>
fix: <what was changed>
files_modified:
- <file path>
regression_risk: low | medium | high
lesson: <what to remember to prevent recurrence>
Examples
Example: Hook fails in non-login shell
Trigger: Post-commit hook throws KeyError: 'HOME' in CI-like environment.
Expected output:
issue: Post-commit hook crashes when HOME not set in non-login sessions
date: 2026-04-06
root_cause: Hook script reads os.environ["HOME"] but non-login shells
(systemd, cron) strip HOME from environment
fix: Guard with os.environ.get("HOME", "/root") fallback + persist HOME
in /etc/environment during install
files_modified:
- .claude/hooks/genesis-hook
- scripts/install_guardian.sh
regression_risk: low
lesson: Never assume HOME exists — non-login shells strip it. Always
use get() with fallback for environment variables in hook scripts.
References
tests/— Test suite for verificationsrc/genesis/learning/procedural/— Procedure updates for recurring patterns
리뷰
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
댓글
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
같은 저장소의 스킬
Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트
Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트
This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and stops at the merge gate for the user's per-PR approval. Do NOT load it for building a feature and opening its PR — that is a build session (`genesis-development`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트
Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트
End-to-end content creation and publishing. Takes a topic (or generates one), drafts in the user's voice, gets approval via Telegram, and publishes to Medium via browser automation. Invoke with "publish a post about X", "write and publish to Medium", "content-publish", or when an ego-dispatched session needs to create and distribute content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
WingedGuardian/GENesis-AGI992026년 10월 19일 업데이트