taskless

Plugin taskless from marketplace taskless in review-bench/taskless_skills. Commands read from the repo's manifest — 1 month ago.

Skills (17)

• code-review

  Perform code reviews following engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.

• code-simplifier

  Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

• commit

  ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

• iterate-pr

  Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

• openspec-apply-change

  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

• openspec-archive-change

  Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

• openspec-bulk-archive-change

  Archive multiple completed changes at once. Use when archiving several parallel changes.

• openspec-continue-change

  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

• openspec-explore

  Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

• openspec-ff-change

  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

• openspec-new-change

  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

• openspec-onboard

  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

• openspec-propose

  Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

• openspec-sync-specs

  Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

• openspec-verify-change

  Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

• pr-writer

  ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Taskless conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push

• taskless

  Use for any Taskless task. Trigger when the user mentions Taskless by name, or when their request involves the .taskless/ directory or files in it (rules, rule-tests, rule-metadata). Specifically: - "create/add/write a taskless rule for X" - "improve/fix/iterate on this taskless rule" - "delete/remo

Slash commands (1)

• /taskless:tskl:tskl

  Run any Taskless action — create/improve/delete a rule, run check, manage auth, or wire CI. Routes via `npx @taskless/cli help <topic>` to fetch the canonical recipe and follow it.