vision
Create or review a high-level vision document capturing project goals and purpose. Use when asked to "define the vision", "what is this project", "set goals", or when starting a new project that needs clarity o...
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Create or review a high-level vision document capturing project goals and purpose. Use when asked to "define the vision", "what is this project", "set goals", or when starting a new project that needs clarity o...
Clean up completed plans in docs/plans/. Archives or deletes finished plans. Use when asked to "clean up plans", "tidy the docs", "archive old plans", or after completing implementation to remove stale planning...
Quick build for small-to-medium scope work without formal planning. Still uses TDD and verification. Use when asked to "build this", "add a quick feature", "make this change", or for straightforward implementat...
Test strategy and execution. Create test plans, run test suites, or fix failing tests. Use when asked to "run tests", "create test strategy", "fix failing tests", "check coverage", or when you need to verify co...
Execute an implementation plan task-by-task with TDD and continuous quality checks. Use when asked to "implement the plan", "execute the tasks", "start building from the plan", or after /arc:detail has created...
Smart commit and push with auto-splitting across domains. Creates atomic commits. Use when asked to "commit", "push changes", "save my work", or after completing implementation work. Automatically groups change...
Run expert review on a plan with parallel reviewer agents. Presents findings as Socratic questions. Use when asked to "review the plan", "get feedback on the design", "check this approach", or before implementa...
Apply Arc's coding rules to the current project. Copies rules to .ruler/ directory. Use when asked to "set up coding rules", "apply standards", "configure rules", or when starting a project that should follow A...
Opinionated recommendations for what to work on next based on tasklist and codebase. Use when asked "what should I work on", "what's next", "suggest priorities", or when starting a session and unsure where to b...
Manages GitLab projects. Use for listing, editing, archiving, sharing projects. Triggers: repo management.
Manages GitLab groups. Use for listing, editing groups, subgroups, projects, or merge requests. Triggers: group management, namespaces.
Manages GitLab releases. Use for creating, updating, deleting releases and assets. Triggers: versioning, deployments.
Manages GitLab merge requests. Use for creating, listing MRs across projects or groups. Triggers: PRs, code reviews.
Handles custom GitLab API requests. Use for any endpoint not covered by other skills. Triggers: advanced API calls, extensions.
Manages GitLab pipelines. Use for listing, running pipelines. Triggers: CI triggers.
Manages GitLab branches. Use for listing, creating, deleting, or querying branches in projects. Triggers: branch operations, git branching.
Manages GitLab runners. Use for registering, updating, deleting runners at various levels. Triggers: CI infrastructure.
Manages GitLab pipeline schedules. Use for creating, editing, running scheduled pipelines. Triggers: cron jobs, automation.
Manages protected branches in GitLab. Use for protecting/unprotecting branches, code owner approvals. Triggers: branch protection.
Manages GitLab tags. Use for creating, deleting, protecting tags. Triggers: versioning.
Manages GitLab packages. Use for listing, publishing, or downloading packages. Triggers: artifact registry.
Manages GitLab deploy tokens. Use for creating, listing, or deleting tokens at instance, project, or group levels. Triggers: deploy keys, access tokens.
Manages GitLab environments. Use for creating, updating, deleting, or protecting deployment environments. Triggers: CI/CD environments, deployments.
Manages GitLab commits. Use for listing, creating, reverting, or querying commit details/diffs/comments. Triggers: commit history, changes, reversions.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.