Explore skills
Showing 16501–16530 of 71536 skills
Transition an Incan RFC from one status to the next. Use when the user asks to promote, advance, or finalize an RFC, or says /bump-rfc. Handles Draft → Planned, Planned → In Progress, and In Progress → Implemented transitions.
encero-systems/incan
Stars: 74Claude CodeCodexSafely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.
encero-systems/incan
Stars: 74Claude CodeCodexDrafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.
encero-systems/incan
Stars: 74Claude CodeCodexGenerate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.
encero-systems/incan
Stars: 74Claude CodeCodexFix actionable in-scope findings in the current Incan worktree, usually after /review. Use when the user asks to fix review findings, clean up reported issues, apply in-scope review feedback, or says /fix.
encero-systems/incan
Stars: 74Claude CodeCodexDetect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.
encero-systems/incan
Stars: 74Claude CodeCodexReport which local git worktrees under tmp/ are safe to close, need a human look, or are explicitly protected. Use when the user says /fleet-audit, asks what worktrees can be cleaned up, or wants a status check across all Ralph-loop/spike worktrees before running closeout on any of them.
encero-systems/incan
Stars: 74Claude CodeCodexOrchestrate a named multi-skill loop such as /loop /review /fix until clean or blocked. Use when the user explicitly asks to loop skills, rerun a review/fix cycle, or says /loop with one or more skill names.
encero-systems/incan
Stars: 74Claude CodeCodexDecompose a task into safe parallel sub-agent slices with explicit ownership, optional worktree isolation, per-worker plans, verification, and orchestrator-led integration. Use when the user explicitly asks for delegation, sub-agents, or parallel work and the task can be split into non-overlapping scopes.
encero-systems/incan
Stars: 74Claude CodeCodexRun a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.
encero-systems/incan
Stars: 74Claude CodeCodexPerform a thorough, Incan-project-aware code review. Use when the user asks for a review, code critique, PR review, or says /review. Checks Rust anti-patterns, compiler pipeline completeness, error handling, test coverage, style conventions, and RFC compliance specific to the Incan compiler codebase.
encero-systems/incan
Stars: 74Claude CodeCodexReview touched subsystems for layering, crate boundaries, single-source-of-truth rules, registry-driven behavior, and compiler/runtime separation. Use when a broad review needs a dedicated architecture pass or when the user asks for architectural review specifically.
encero-systems/incan
Stars: 74Claude CodeCodexReview touched code for maintainability smells such as duplication, awkward indirection, suspicious clones, dead code, poor naming, and Boy Scout cleanup opportunities. Use when a broad review needs a dedicated maintainability pass or when the user asks for code-smell review specifically.
encero-systems/incan
Stars: 74Claude CodeCodexReview user-facing docs, CLI reference text, examples, and scaffolds for truthfulness, prose quality, and RFC leakage. Use when a broad review needs a dedicated docs/claims pass or when the user asks for docs-truth review specifically.
encero-systems/incan
Stars: 74Claude CodeCodexReview touched Incan source for Python-quality readability, idiomatic Incan structure, dogfooding integrity, public API polish, and source-level anti-patterns. Use for `.incn` stdlib, examples, language-surface implementations, or when the user asks whether Incan code reads like well-written Python rather than Rust-shaped scaffolding.
encero-systems/incan
Stars: 74Claude CodeCodexOrchestrate a broad Incan review using specialized reviewer roles, parallel slice reports, and a canonical merged review report. Use when the user asks for delegated review, multi-agent review, or when a broad dirty worktree should be reviewed by specialized passes rather than one generic reviewer.
encero-systems/incan
Stars: 74Claude CodeCodexReview an Incan RFC document for formatting, structural, and content issues before GitHub submission. Use when the user asks to review an RFC, check an RFC for problems, prepare an RFC for submission, or says /review-rfc.
encero-systems/incan
Stars: 74Claude CodeCodexReview touched Rust files for prose-comment quality, rustdoc accuracy, and manually chopped comment wrapping. Use when a broad review needs a dedicated Rust prose/rustdoc pass or when the user asks for comment-quality review specifically.
encero-systems/incan
Stars: 74Claude CodeCodexReview a change against issue, RFC, branch, and user-request scope. Use when a broad review needs a dedicated scope/completeness pass or when the user asks whether the implementation actually matches the intended surface.
encero-systems/incan
Stars: 74Claude CodeCodexReview touched tests and test-adjacent code for style, Result-returning patterns, panic helpers, unwrap/expect use, and obvious coverage gaps. Use when a broad review needs a dedicated test pass or when the user asks for test-review specifically.
encero-systems/incan
Stars: 74Claude CodeCodexPrepare to work on a GitHub issue or RFC. Use when the user says /start-work, asks to start an issue, begin an RFC implementation, or pick up a task. Creates the branch, gathers context, and checks learnings.
encero-systems/incan
Stars: 74Claude CodeCodexRun and write tests for the Incan compiler. Use when the user asks to test changes, add tests, run the test suite, verify a feature, or says /test. Guides test selection, provides correct patterns, and runs the right commands.
encero-systems/incan
Stars: 74Claude CodeCodexDraft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.
encero-systems/incan
Stars: 74Claude CodeCodexDraft a new RFC document for the Incan language project. Use when the user asks to write, create, or draft an RFC, or wants to propose a new language feature or infrastructure change for Incan.
encero-systems/incan
Stars: 74Claude CodeCodexCreate a pull request
adamayoung/TMDb
Stars: 180Claude CodeCodexThis skill should be used when the user asks to "polish the UI", "improve product UX", "design app controls", "reduce friction", or "create design rules". Design usable, distinctive product interfaces for new or existing apps.
fcakyon/claude-codex-settings
Stars: 1.2kClaude CodeCodexTransfers prose edits from latex/index.tex (Overleaf) back into index.qmd. Use after pulling LaTeX edits from a collaborator.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexThis skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".
fcakyon/claude-codex-settings
Stars: 1.2kClaude CodeCodexThis skill should be used when the user asks to "build an AEO strategy", "improve AI search visibility", "track buyer prompts", "analyze AI citations", or "plan content for answer engines". Apply an evidence-led answer engine optimization (AEO/GEO) feedback loop to any product or service, prioritizing discovery by buyers who have not heard of it.
fcakyon/claude-codex-settings
Stars: 1.2kClaude CodeCodexThis skill should be used when the user asks to "verify UI changes", "audit UI quality", "test every screen and action", "run regression QA", "check a deployed UI", or "validate an extension release". Test known web and browser-extension workflows on localhost, staging, or production with action coverage, recovery, localization, accessibility, and real integration evidence. Use dogfood for open-ended bug discovery.
fcakyon/claude-codex-settings
Stars: 1.2kClaude CodeCodex