refactor

スター11

フォーク4

更新日2026年6月25日 09:36

Use when cleaning or refactoring this Gorkie Slack codebase. Covers the local cleanup style: simplifying names, collapsing thin helpers, splitting real ownership boundaries, trimming tool schemas, preserving Slack/AI behavior, and running the repo validation suite.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

imdevarsh

imdevarsh/gorkie

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Gorkie Refactor

Clean by reducing jumps, not by adding architecture.

Pass Shape

Read the nearby source first. Do not rename or split from vibes.
Find names that describe implementation history instead of current purpose. Prefer direct names like reply, turns, buildPrompt, annotateMentions.
Collapse helpers that only wrap one line or have no ownership. Inline them at the call site unless they hide a real boundary.
Split files only when a module owns a coherent concept: turn state, compaction, sandbox setup, Slack mention annotation, tool factories, task rendering.
Make factory naming consistent. If most factories use *Tool, fix outliers without changing model-facing tool keys.
Keep schemas terse. Add .describe() only for fields whose contract is not obvious from the name.
Keep type ownership explicit. Private one-file shapes stay inline; shared or exported shapes live in the nearest clear owner types/ folder. App-wide bot shapes can live under apps/bot/src/types/. Tool-owned shared shapes use a types/tools/<tool>.ts path.
Remove stale docs and prompts after renames. Search for old names before handoff.

Gorkie-Specific Smells

index.ts files that own lifecycle, state, IO, and helpers at once.
create*, build*, with*, resolve* names that hide a tiny operation.
Three optional fields where a discriminated shape is clearer.
Long async closures inside tool factories or object literals.
User-facing task names that describe internal status instead of the action.
Exported interfaces living in implementation files when an owned types/ folder is the clearer home.
Tool-owned shared types outside a types/tools/ folder.
Stale prompt/docs references after tool or agent module renames.

Validation

After code changes, run:

bun run fix
bun run typecheck
bun run check
bun run check:spelling
bun run check:knip

For file moves, deleted exports, or public entry points, also run stale-name searches with rg and, when practical, a non-starting import smoke.

このリポジトリの他の Skills

同じリポジトリ

slack-agent

imdevarsh/gorkie

Use when working on Slack agent/bot code, Chat SDK applications, Bolt for JavaScript projects, or projects using @chat-adapter/slack or @slack/bolt. Provides development patterns, testing requirements, and quality standards.

2026-06-2011

agentmail

imdevarsh/gorkie

Give AI agents their own email inboxes using the AgentMail API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, handling attachments, organizing with labels, creating drafts for human approval, or setting up real-time notifications via webhooks/websockets. Supports multi-tenant isolation with pods.

2026-06-1911

chat-sdk

imdevarsh/gorkie

Build multi-platform chat bots with Chat SDK (`chat` npm package). Use when developers want to build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI streaming, set up webhook routes or multi-adapter bots, send rich cards or streamed AI responses to chat platforms, or build a custom adapter or state adapter.

2026-06-1411

coding-best-practices

imdevarsh/gorkie

Code quality rules for the Gorkie Slack bot. Use when reviewing files for violations, auditing PRs, or deciding how to structure new code. Covers TypeScript patterns, Slack modal conventions, and architecture rules specific to this repo.

2026-06-0711

turborepo

imdevarsh/gorkie

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

2026-05-2311

Gorkie Refactor

Clean by reducing jumps, not by adding architecture.

Pass Shape

Read the nearby source first. Do not rename or split from vibes.

Find names that describe implementation history instead of current purpose. Prefer direct names like reply, turns, buildPrompt, annotateMentions.

Collapse helpers that only wrap one line or have no ownership. Inline them at the call site unless they hide a real boundary.

Split files only when a module owns a coherent concept: turn state, compaction, sandbox setup, Slack mention annotation, tool factories, task rendering.

Make factory naming consistent. If most factories use *Tool, fix outliers without changing model-facing tool keys.

Keep schemas terse. Add .describe() only for fields whose contract is not obvious from the name.

Keep type ownership explicit. Private one-file shapes stay inline; shared or exported shapes live in the nearest clear owner types/ folder. App-wide bot shapes can live under apps/bot/src/types/. Tool-owned shared shapes use a types/tools/<tool>.ts path.

Remove stale docs and prompts after renames. Search for old names before handoff.

Gorkie-Specific Smells

index.ts files that own lifecycle, state, IO, and helpers at once.

create*, build*, with*, resolve* names that hide a tiny operation.

Three optional fields where a discriminated shape is clearer.

Long async closures inside tool factories or object literals.

User-facing task names that describe internal status instead of the action.

Exported interfaces living in implementation files when an owned types/ folder is the clearer home.

Tool-owned shared types outside a types/tools/ folder.

Stale prompt/docs references after tool or agent module renames.

Validation

After code changes, run:

bun run fix bun run typecheck bun run check bun run check:spelling bun run check:knip

For file moves, deleted exports, or public entry points, also run stale-name searches with rg and, when practical, a non-starting import smoke.

name	refactor
description	Use when cleaning or refactoring this Gorkie Slack codebase. Covers the local cleanup style: simplifying names, collapsing thin helpers, splitting real ownership boundaries, trimming tool schemas, preserving Slack/AI behavior, and running the repo validation suite.