verify-changes
Skill2.4k starsChanged 14 days agoLGPL-2.1View on GitHub
Select and run focused builds, tests, and executable checks for MOOSE changes, with a mandatory environment gate, protection against stale binaries, and evidence-based results. Use when someone asks to build, test, or verify MOOSE work; before claiming that changed MOOSE behavior works; or when another MOOSE workflow needs verification for a pull request, review response, bug fix, or feature.
12 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- mab-go/xmind-mcptheir own version, first seen Nov 8, 2026
- FilenCloudDienste/filen-rstheir own version, first seen Oct 9, 2026
- vudovn/ag-kittheir own version, first seen Oct 8, 2026
- foru17/neko-mastertheir own version, first seen Oct 8, 2026
- foru17/clash-mastertheir own version, first seen Oct 8, 2026
- vudovn/antigravity-kittheir own version, first seen Oct 8, 2026
Who's talking about idaholab/moose
- @ponceto91.bsky.social“Bonjour et bon vendredi ! Si vous vous intéressez aux solveurs dans le but d'effectuer des simulations …”Bluesky · Jan 26, 2024 · 2 likes
- idaholab/tmap8“Addition of Scalar Thermal-Hydraulic System Representation”GitHub · Sep 22, 2026 · 1 reactions
- libMesh/libmesh“Fix GhostPointNeighbors::mesh_reinit()”GitHub · Jan 9, 2026 · 1 reactions
- libMesh/libmesh“Adaptivity improvements”GitHub · Jun 3, 2025 · 1 reactions
- libMesh/libmesh“Better error when asked to tetrahedralize a broken boundary”GitHub · Aug 7, 2024 · 1 reactions
The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 51
Talked about on GitHub and Bluesky (51 times).
On GitHub · 50
- Sep 22, 2026Addition of Scalar Thermal-Hydraulic System Representation — idaholab/tmap81 reaction · 1 comment
- Jan 9, 2026Fix GhostPointNeighbors::mesh_reinit() — libMesh/libmesh1 reaction · 3 comments
- Jun 3, 2025Adaptivity improvements — libMesh/libmesh1 reaction · 4 comments
- Aug 7, 2024Better error when asked to tetrahedralize a broken boundary — libMesh/libmesh1 reaction · 3 comments
- Apr 4, 2024Increased functionality for CondensedEigenSystem — libMesh/libmesh1 reaction · 11 comments
45 more on GitHub
- Sep 26, 2023Rename heat conduction module to heat transfer — idaholab/malamute1 reaction · 2 comments
- Dec 7, 2022/mpi/openmpi/4.1.4-gnu-10.2/lib64/libopen-pal.so: undefined reference to fi_open@FABRIC_1.5'` — open-mpi/ompi1 reaction · 8 comments
- Feb 8, 2021includes in NEML getting mixed up with std library — idaholab/blackbear1 reaction
- May 28, 2020Update for API changes — lcpp-org/crane1 reaction · 3 comments
- May 28, 2020Upcoming API change in MOOSE — lcpp-org/crane1 reaction
- Jul 27, 2017Unclosed filehandle build-up in FParser JIT compile — libMesh/libmesh1 reaction · 4 comments
- Nov 4, 2026Fixed syntax for a link — idaholab/mastodon0 reactions · 4 comments
- Nov 1, 2026auto_update_moose: bump moose from `ddf1954` to `738016c` — arfc/moltres0 reactions
- Oct 24, 2026Update limit on output name length in YHx tests. — idaholab/tmap80 reactions
- Oct 22, 2026Rename RobinBC to avoid naming conflict in moose framework — arfc/squirrel0 reactions · 4 comments
- Oct 7, 2026SCM_radial_conduction_bug — idaholab/virtual_test_bed0 reactions
- Oct 7, 2026Important SCM source code change requires VTB regolding — idaholab/virtual_test_bed0 reactions
- Oct 6, 2026TEAM Problem 7 Benchmark — aurora-multiphysics/canarysays it tested it0 reactions
- Oct 1, 2026auto_update_moose: bump moose from `1629329` to `ddf1954` — arfc/moltres0 reactions
- Sep 9, 2026TEAM Problem 13 Benchmark — aurora-multiphysics/canarysays it tested it0 reactions
- Sep 9, 2026Variational smoother was seen to tangle an element in a mixed quad-tri mesh — libMesh/libmesh0 reactions
- Aug 18, 2026Make sure we use the new gradient request terminology. — idaholab/open_pronghorn0 reactions · 1 comment
- Aug 18, 2026Update gradient request to enable moose submodule update. — idaholab/open_pronghorn0 reactions
- Jul 21, 2026Simple generic pbr — idaholab/virtual_test_bed0 reactions · 1 comment
- May 14, 2026GhostingFunctor subclasses *themselves* should `unset_has_reinit_ghosting_functors()` when needed — libMesh/libmesh0 reactions
- Apr 3, 2026Unit system in divertor monoblock example — idaholab/tmap80 reactions · 2 comments
- Mar 23, 2026Mesh is unexpectedly unprepared after (or before?) stitching — libMesh/libmesh0 reactions
- Mar 20, 2026Update concrete logarithmic creep model for moose viscoelasticy updates — idaholab/blackbear0 reactions
- Mar 4, 2026Modified wells coupling example to add injection of H2 with the water — idaholab/falcon0 reactions
- Feb 24, 2026Reduce heap allocation in solid-mechanics plasticity — idaholab/blackbear0 reactions
- Dec 5, 2025Andy on 30853 — hugary1995/moose0 reactions · 6 comments
- Apr 24, 2025Build libmesh (without --enable-complex) with PETSc (with complex scalars) — libMesh/libmesh0 reactions · 2 comments
- Mar 21, 2025Explicitly defining material property output to CSV object when expected by tester — idaholab/blackbear0 reactions
- Mar 17, 2025Add an option to prevent coarsening of elements with different subdomain IDs — libMesh/libmesh0 reactions
- Sep 14, 2024Bump moose from `bd59058` to `8cd741c` — gsgall/gsgall.github.io0 reactions
- Sep 12, 2024ExodusII_IO_Helper: do not crash when outputting subdomains without elements — libMesh/libmesh0 reactions · 1 comment
- Dec 4, 2023Some tests will diff if the initial residual evaluation is skipped — shannon-lab/zapdos0 reactions · 1 comment
- May 24, 2023Make curvature signs consistent between 2D and 3D — libMesh/libmesh0 reactions
- Sep 26, 2022Output desired size when AD container size is exceeded — roystgnr/MetaPhysicL0 reactions · 6 comments
- Mar 12, 2022ExodusII_IO::set_output_variables may pass in invalid variable names — libMesh/libmesh0 reactions
- Oct 11, 2018Comparing Ghosting Functors — libMesh/libmesh0 reactions · 5 comments
- Jan 17, 2018Replace UserForcingFunction with BodyForce in tests — jessecarterMOOSE/PRARIEDOG0 reactions
- Nov 13, 2017New Utility in boundary_info to check for sideset == nodeset equality — libMesh/libmesh0 reactions
- Sep 22, 2017New System::point_*() APIs — libMesh/libmesh0 reactions
- Feb 24, 2017build_node_list_from_side_list can fail on distributed meshes — libMesh/libmesh0 reactions
- Mar 10, 2016Random test failures — RedbackProject/redback0 reactions · 5 comments
- Apr 24, 2015Constraint to enforce matching of gradients across boundaries — libMesh/libmesh0 reactions · 14 comments
- Feb 19, 2015Adding support for dynamic multiapps — japnp/ANT0 reactions
- Feb 19, 2015Adding support for dynamic multiapps — whtblk/littlegrass0 reactions
- Feb 19, 2015Adding support for dynamic multiapps — phleveque/mef0 reactions
On Bluesky · 1
- Jan 26, 2024Bonjour et bon vendredi ! Si vous vous intéressez aux solveurs dans le but d'effectuer des simulations physiques, regardez du côté de… — @ponceto91.bsky.social2 likes and reposts
Used with
Projects with it also use intelligent-routing, design-spec and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SKB3002Skillintelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Also in 3 projects that use this
jornalistainclusivoSkilldesign-spec
How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.
Also in 3 projects that use this
xenitV1Skillbash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
Also in 3 projects that use this
- xenitV1Skill
red-team-tactics
Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.
Also in 3 projects that use this
xfstudioSkillrust-pro
Master Rust 1.75+ with modern async patterns, advanced type system
Also in 3 projects that use this
- +7 more from xenitV1
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- foru17/clash-master★ 4.2ksame name
- foru17/neko-master★ 4.2ksame name
- h0x91b/dev-3.0★ 329same name
- FilenCloudDienste/filen-rs★ 104same name
- mab-go/xmind-mcp★ 9same name
- zzfancitizen/agent-skills-self-learning-sample★ 3same name
- 26zl/universal-agent-skills★ 2same name
- gillkyle/skills★ 1same name
2 more not listed
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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brittle-numerics-root-causeSkill
- civet-ci-failuresSkill
- codegraphSkill
- issue-createSkill
- moose-docsSkill
- paraview-exodusSkill
- pr-address-reviewSkill
- pr-createSkill
- pr-reviewSkill
- run-testsSkill
- update-packagesSkill
- write-regression-testsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.