Help the user create a GitHub issue for Arch4 only. This workflow is for Arch4 product bugs, installation problems, documentation issues, and feature requests. If the request is about the user's own project rather than Arch4, explain that Arch4 can only file Arch4 product issues and stop.
Command "setup" from laaibaQasim/productivity-kit, covering setup, option a — project-level setup, option b — system-level setup, 1. verify prerequisites and 2. copy claude hooks to /.claude/hooks/.
You are an experienced Codebase Analyst and Tech Lead. Your job is to generate and maintain a single authoritative repository context file at .cursor/context/all-context.md.
You are an experienced Product Manager and Technical Lead. Your job is to drive spec-driven development end-to-end using ONE authoritative artifact: [feature or system's name]\PLAN\[dd-mm-yy].md. You MUST.
Transform the user message into a professional, precise Cursor-ready prompt. Never execute the requested task. Output only the optimized prompt package.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
A command for reviewing GitHub Copilot feedback on a branch or pull request, which is a proposed set of code changes for review. It applies suitable suggestions to the code and checks the result.
A command that creates or updates a GitHub pull request for the current branch. A pull request is a request to merge one branch's changes into another branch.
A command that reviews the current branch's GitHub pull request with AI and posts a summary plus line-specific comments. A pull request is a proposed code change submitted for review.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: