ahgraber
@ahgraber
Public Skills
proof
by ahgraber
"Use when the user asks for proofreading or light copy editing while preserving original wording, tone, and order. Triggers: 'proofread', 'fix typos', 'grammar only', 'copy edit only', 'SPAG pass'. Not for rewrites, tone shifts, structural edits, or style upgrades; use good-prose for those requests."
handoff
by ahgraber
"Use when ongoing work must continue in a new conversation, session, or agent with no shared history. Triggers: 'handoff', 'prepare context for next chat', 'summarize for a new session', 'continue this in another conversation'. Not for same-chat status updates or repository documentation."
shell-scripts
by ahgraber
Use when writing or reviewing Bash scripts and shell snippets, especially for shebang selection, quoting, parameter expansion ("${VAR}" style), test expressions ([ ] vs [[ ]]), ShellCheck-guided fixes, and portability decisions across POSIX sh, Bash, and zsh compatibility targets.
commit-message
by ahgraber
"Use when drafting a Conventional Commit message from currently staged Git changes. Triggers: 'write commit message', 'draft commit from staged changes', 'generate conventional commit', 'message for git commit -F -'. Not for creating commits, amending history, or full code review."
code-review
by ahgraber
"Use when reviewing code changes before committing or merging — staged diffs, branch diffs, or PR readiness checks. Triggers: 'review my code', 'check these changes', 'review this branch', 'give feedback on my diff', 'is this PR ready?'. Not for implementing features, running test suites, or formatting-only passes."
spec-kit-plan
by ahgraber
Use when an approved Spec Kit spec.md must be translated into technical design artifacts (plan.md, research.md, data-model.md, contracts/, quickstart.md) before spec-kit-tasks, or when plan.md is missing/outdated after spec or constitution changes.
spec-kit
by ahgraber
Use when work involves Spec Kit and you need to choose the correct spec-kit-* sub-skill, enforce artifact-order gates, or route remediation work (for example sequence violations or specification drift at any stage).
spec-kit-tasks
by ahgraber
Use when an approved Spec Kit plan.md + spec.md must be decomposed into dependency-ordered tasks.md, or when tasks.md is missing/stale after planning or reconciliation changes.
spec-kit-reconcile
by ahgraber
Use when specification drift is discovered at any stage and existing Spec Kit artifacts (spec.md, plan.md, tasks.md) must be reconciled in-place without creating a new feature branch.
spec-kit-clarify
by ahgraber
Use when an existing Spec Kit spec.md has high-impact ambiguity (for example [NEEDS CLARIFICATION], unresolved scope decisions, or unquantified requirements) that must be resolved before spec-kit-plan.
spec-kit-implement
by ahgraber
Use when approved Spec Kit tasks.md must be executed into implementation changes, or when task execution is blocked by sequencing/checklist gates before feature completion.
spec-kit-analyze
by ahgraber
Use when spec.md, plan.md, and tasks.md exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
spec-kit-specify
by ahgraber
Use when a Spec Kit feature needs spec.md authored or rewritten from natural-language requirements, especially when the feature has no usable specification or requirements are too vague for planning.
spec-kit-checklist
by ahgraber
Use when a Spec Kit feature has spec.md and you need a requirements-quality checklist (clarity, completeness, consistency, measurability, coverage), not implementation/runtime test cases.
spec-kit-constitution
by ahgraber
Use when creating or amending a Spec Kit project constitution, especially when memory/constitution.md is missing, contains [PLACEHOLDER] tokens, or principle changes must be propagated to planning/spec/task templates.
optimize-skills
by ahgraber
Use when creating or refining SKILL.md-based skills, or diagnosing weak triggering (under/over-triggering, vague descriptions, bloated context, or missing workflow guidance).
mcp-research
by ahgraber
Use when tasks require current, source-backed technical information from MCP tools. Apply for library/API questions, dependency version checks, third-party integration work, framework- or SDK-specific debugging, and any case where stale model knowledge could cause incorrect guidance.
python-design-modularity
by ahgraber
Use when designing module boundaries, planning refactors, or reviewing architecture in Python codebases. Also use when facing tangled dependencies, god classes, deep inheritance hierarchies, unclear ownership, or risky structural changes.
python-errors-reliability
by ahgraber
Use when designing error handling, retry policies, timeout behavior, or failure classification in Python. Also use when code swallows exceptions, loses error context across boundaries, has unbounded retries, silent failures, or lacks idempotency guarantees on retried writes.
python-data-state
by ahgraber
Use when designing data ownership, validation boundaries, consistency models, or configuration strategy in Python. Also use when encountering unclear ownership across modules, shared mutable state leaking between layers, validation gaps at ingress, cross-module transactional coupling, or config drift between environments.
python-workflow-delivery
by ahgraber
Use when preparing branches, commits, or PRs for Python changes — scoping work, running validation gates, and ensuring merge readiness. Also use when debugging CI gate failures, resolving lockfile conflicts, or uncertain what checks to run before opening a PR.
python-runtime-operations
by ahgraber
Use when building or reviewing service, job, or CLI runtime behavior in Python — designing startup validation, shutdown sequences, observability, and structured logging. Also use when startup crashes from late config, shutdown leaves orphaned processes, terminal states are implicit, or logs lack structure.
python-types-contracts
by ahgraber
Use when defining or evolving public interfaces, schema boundaries, or pydantic usage in Python. Also use when annotations are missing on public APIs, pydantic models appear everywhere instead of at trust boundaries, contract changes lack migration guidance, or Any/object types are overused across module boundaries.
python-notebooks-async
by ahgraber
"Use when writing or reviewing asyncio code in Jupyter notebooks or '#%%' cell workflows — structuring event-loop ownership, orchestrating async tasks, or choosing compatibility strategies. Also use when hitting RuntimeError: This event loop is already running, asyncio.run() failures in cells, or tasks silently never completing."