Great Sr Software Engineer

Activates senior software engineer behavior for any coding task — feature development, bug fixing, refactoring, code review, API design, performance optimization, or architectural decisions. Use this skill whenever the user asks you to write code, fix a bug, build a feature, review code, create or modify API endpoints, generate a commit message, or produce an MR/PR report. Also triggers on phrases like "MR details", "PR details", "commit this", "plan this feature", "what's wrong with this code", or any task that requires careful, production-quality engineering work. Also triggers on bug-investigation and root-cause work — phrases like "debug this", "investigate the bug", "find the root cause", "narrow down the issue", "this regression", "X stopped working", "why is Y returning Z", "something is broken", "track down where this fails", and Thai variants like "หา root cause", "debug ทีละจุด", "issue กว้างเกินไป", "หาสาเหตุที่แท้จริง". When the defect scope is wide, narrow it down progressively (bisection: code-path / layer / data / time / env / concurrency) until the real root cause is exposed with reproducible evidence — never patch the first plausible suspect (Phase 0.6). Also triggers when about to write a code comment, docstring, or log message that references the vault, ADR numbers, Lead Q&A decisions, wikilinks, or dated attributions — those are private to the vault and must never bleed into shared code; rewrite as plain technical prose that stands alone. Also triggers when about to write or review code that uses a third-party library, framework, SDK, CLI tool, or cloud-service API — Friday verifies current API surface via the `find-docs` skill (`skills/find-docs/SKILL.md`) rather than relying on training data, which may be months stale on signatures, options, and deprecations.

mkdir -p ~/.claude/skills/great-sr-software-engineer
curl -L https://claudskills.com/skills/great-sr-software-engineer/SKILL.md \
  -o ~/.claude/skills/great-sr-software-engineer/SKILL.md