foyzulkarim

foyzulkarim/skills

Plugin Claude Code

Claude Code plugin marketplace with a structured development pipeline.

foyzulkarim/skills

Instructions file CodexOpenCode

AGENTS.md instructions for foyzulkarim/skills, covering agents.md — foyzulkarim/skills, repo nature, developer commands, local testing workflow (scripts/sync-skills.sh) and pipeline artifacts on master.

foyzulkarim/skills

Instructions file

Claude Code instructions for foyzulkarim/skills, covering claude.md, what this repo is, the 5-phase pipeline + qa gate, plugin structure and the pipeline.

foyzulkarim/skills

Plugin Claude Code

A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…

foyzulkarim/skills

Skill Claude CodeCodex

Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.

foyzulkarim/skills

Skill Claude CodeCodex

One-shot conventional commit; bundled scripts adaptively gather diff context, draft the message, and stage+commit — pass ask to confirm first or add a hint for the title. Use only when the user asks for a commit.

foyzulkarim/skills

Skill Claude CodeCodex

Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…

foyzulkarim/skills

Skill Claude CodeCodex

After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/ ), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.

foyzulkarim/skills

Skill Claude CodeCodex

Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.

foyzulkarim/skills

Skill Claude CodeCodex

Phase 4 of 5 — implements tasks from TASKS- - .md (with ARCH- - .md as architecture-only context) using mode-appropriate verification (tdd, test-after, ui, checklist); pass 'auto' to run without stepping. Use only when the user asks to run Phase 4 or implement tasks from an ARCH doc — never trigger automatically from…

foyzulkarim/skills

Skill Claude CodeCodex

After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/ ) 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

Skill Claude CodeCodex

Phase 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

Skill Claude CodeCodex

Post-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- - .md) that /execute-qa…

foyzulkarim/skills

Skill Claude CodeCodex

Phase 1 of 5 — Socratic interview capturing WHAT and WHY; outputs a sprint-sized REQ doc for plan-architecture. Use only when the user asks to run Phase 1, plan requirements, or start the requirements interview — never trigger automatically from a feature description.

foyzulkarim/skills

Skill Claude CodeCodex

Draft 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

Skill Claude CodeCodex

Phase 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

Skill Claude CodeCodex

Render 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.…

foyzulkarim/skills

Skill Claude CodeCodex

Install 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

Skill Claude CodeCodex

Bootstrap 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…

foyzulkarim/skills

Skill Claude CodeCodex

Copy 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.