Explore skills
Showing 41701–41730 of 71536 skills
After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/<issue#>) and return the primary checkout to current main, so the next parallel lane can start. Use when the user says to move the branch or task to a worktree or open a parallel lane.
foyzulkarim/skills
Stars: 43Claude CodeCodexPhase 2 of 5 — collaborative system design plus change-footprint mapping; outputs an ARCH doc for generate-tasks. Use only when the user asks to run Phase 2, plan the architecture, or design the solution — never trigger automatically from a design question.
foyzulkarim/skills
Stars: 43Claude CodeCodexPost-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA-<N>-<slug>.md) that /execute-qa runs. The agent drives browser and shell; the human steps in only at named handoff points. Use only when the user asks to plan manual QA — never trigger automatically.
foyzulkarim/skills
Stars: 43Claude CodeCodexDraft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.
foyzulkarim/skills
Stars: 43Claude CodeCodexPhase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
foyzulkarim/skills
Stars: 43Claude CodeCodexAudit Claude Code session logs (~/.claude/projects) for token waste and produce a ranked, attributed efficiency report (habit / skill_file / config). Use when the user asks to audit session efficiency, analyze token waste or cost blowups, review Claude Code usage cost, or asks "where are my tokens going".
foyzulkarim/skills
Stars: 43Claude CodeCodexRender a dashboard of the current Claude Code session — message counts, token usage, cache read/write, dollar cost, context %, lines changed, cost-per-turn sparkline, and a tool-call histogram — parsed from the session transcript JSONL by a bundled bash script. One bash call, zero analysis, zero confirmation. Optionally pass a session id to inspect a different session. Use when the user asks for session stats, usage, token or cost breakdown, or a session dashboard.
foyzulkarim/skills
Stars: 43Claude CodeCodexInstall genuine per-session cost tracking for Claude Code by wiring bundled logger scripts into the user's statusline — preserving any existing statusline and hooks. Use when the user asks to set up, install, enable, or repair cost tracking / cost logging / session cost capture. Idempotent; safe to re-run.
foyzulkarim/skills
Stars: 43Claude CodeCodexBootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the default branch, creates and pushes the branch, and writes specs/context/<id>.md. Use only when the user explicitly asks to start a task or create a work branch — never trigger automatically.
foyzulkarim/skills
Stars: 43Claude CodeCodexCopy this repo's skills into another agent harness's skills directory by name — resolves the harness alias to its path via scripts/sync-targets.json and runs sync-skills.sh. Use only when the user asks to copy/sync/push the skills to another harness (oh-my-pi, opencode, kimi, codex, etc.) — never trigger automatically.
foyzulkarim/skills
Stars: 43Claude CodeCodexA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexplurigrid/asi
Stars: 72Claude CodeCodexStress-test a plan against domain terminology, code behavior, and existing decisions. Use for domain-model interviews or reconciling glossary and architecture conflicts.
jupes/agent-forge-harness
Stars: 2Claude CodeCodexIdentify architectural friction and compare refactoring opportunities. Use for architecture assessment before selecting an implementation.
jupes/agent-forge-harness
Stars: 2Claude CodeCodex