redmine_ai_helper

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINE_PLAYRIGHT_URL/REDMINE_PLAYRIGHT_USER/REDMINE_PLAYRIGHT_PASSWORD environment variables. Use whenever the user asks to open, check, access, or test something in the running Redmine UI (e.g. verifying a feature in the browser, taking a screenshot of a page, manually exercising a flow).

Stage the current changes and create a git commit with a properly formatted English message. Use whenever the user asks to commit, save, or check in their work. Picks a Conventional-Commits-style prefix (fix:, feat:, refactor:, docs:, test:, chore:, style:, perf:) based on the actual diff, keeps the first line a concise summary, and adds a bullet list of details only when the change touches several things.

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create or update the feature specification from a natural language feature description.

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Generate Redmine.org release notes from a GitHub release tag. Fetches the release, strips emojis/issue numbers/author names, and outputs Textile-formatted text ready to paste into redmine.org.

Create a release branch for a given version. Use when you want to start a release, cut a release branch, or bump the version for a new release. Creates release/<version> from develop, updates version.rb, and commits the version bump.

Create a pull request from the current branch. Use when you want to open a PR, submit changes, or create a pull request. Handles release branches (release/**) and feature/fix branches differently, setting the correct base branch, title, description, and labels automatically.

Set up branch and folder naming rules for the current project

Rename non-compliant branches and spec folders to match the configured convention

Check all feature branches and spec folders against the configured naming convention

Compact one or more Spec-Driven Development artifacts in place to reduce token cost on subsequent /speckit.* commands. Lossless on requirements, decisions, contracts, IDs; strips template scaffolding, examples, and prose padding. The original is preserved as <artifact>.full.md the first time an artifact is compacted.

Toggle a project-local concise-output directive that suppresses agent prose padding during SDD steps. State lives in the project's agent memory file (AGENTS.md preferred when present, else CLAUDE.md / GEMINI.md / .cursor/rules / .windsurf/rules / etc.) inside a clearly marked block, so it is reversible and reviewable.

Build a focused reading manifest for the next workflow step. Names the files the agent should load, the sections it can skip, and the running token budget. Run this *before* /speckit.plan, /speckit.tasks, or /speckit.implement to keep their working context lean.

Show token usage for every SDD artifact in the active feature, the projected context window for each upcoming phase, and the savings already realized by token-budget (full backups vs current files).

Run RuboCop linting and fix offenses for the redmine_ai_helper plugin

Code quality checks, formatting, and metrics via qlty CLI