regression-check
Skill107 starsChanged 9 months agoMITView on GitHub
Run the full regression suite for the redmine_ai_helper plugin (YARD doc coverage, RuboCop, and the plugin test suite) via .devcontainer/regression-check.sh
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Antune-L/skillzertheir own version, first seen Sep 13, 2026
- ayouaiyouwei-arch/claude_pm_workflowstheir own version, first seen Jun 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Antune-L/skillzer★ 11same name
- ayouaiyouwei-arch/claude_pm_workflows★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- commitSkill
- create-pull-requestSkill
- create-release-branchSkill
- create-release-notesSkill
- handle-pr-reviewSkill
- qlty-checkSkill
- record-code-review-feedbackSkill
- record-spec-feedbackSkill
- recreate-test-dbSkill
- redmine-playwright-loginSkill
- rubocopSkill
- speckit-agent-context-updateSkill
- speckit-analyzeSkill
- speckit-branch-convention-configureSkill
- speckit-branch-convention-renameSkill
- speckit-branch-convention-validateSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-review-codeSkill
- speckit-review-commentsSkill
- speckit-review-errorsSkill
- speckit-review-runSkill
- speckit-review-simplifySkill
- speckit-review-testsSkill
- speckit-review-typesSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-token-budget-compactSkill
- speckit-token-budget-conciseSkill
- speckit-token-budget-scopeSkill
- speckit-token-budget-usageSkill
- speckit-wiki-ingestSkill
- speckit-wiki-initSkill
- speckit-wiki-lintSkill
- speckit-wiki-querySkill
- speckit-wiki-statusSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the plugin's full regression check: YARD documentation coverage, RuboCop linting, and the complete Minitest suite.
- Very specific: line 40
Must be run from a shell that can cd into /usr/local/redmine — the script assumes the plugin lives at …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Regression Check
Run the plugin's full regression check: YARD documentation coverage, RuboCop linting, and the complete Minitest suite.
Workflow
Step 1: Run the regression script
sh -x .devcontainer/regression-check.shThe script (.devcontainer/regression-check.sh) does the following, in order, aborting on the first failure (set -ex):
cdinto the plugin rootyard stats --list-undoc | tee /dev/stderr | grep -q "100.00%"— fails if documentation coverage drops below 100%rubocop— fails on any offensecd /usr/local/redminethenbundle exec rake redmine:plugins:test— runs the full Redmine test suite (all plugins, not justNAME=redmine_ai_helper)
Step 2: Triage failures
- YARD gap: find the newly undocumented module/class/method/constant/attribute and add a doc comment.
- RuboCop offense: fix per the
rubocopskill's guidelines (see.claude/skills/rubocop/SKILL.md); never relax.rubocop.ymlthresholds without explicit user approval. - Test failure/error: investigate the failing test, fix the underlying code (never disable or delete the test to make it pass), then re-run.
Step 3: Re-run until clean
Re-run the script after each fix until it exits 0 with:
100.00% documentedno offenses detected0 failures, 0 errors, 0 skips
Notes
- Must be run from a shell that can
cdinto/usr/local/redmine— the script assumes the plugin lives at/usr/local/redmine/plugins/redmine_ai_helper. - This runs the entire Redmine test suite (all plugins), which takes noticeably longer than
rake redmine:plugins:test NAME=redmine_ai_helper. Use the narrowerNAME=form for quick iteration while fixing a single test, and this skill for the final full check.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

