aboutsummaryrefslogtreecommitdiff
path: root/review-code
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-06 07:32:53 -0500
committerCraig Jennings <c@cjennings.net>2026-06-06 07:32:53 -0500
commitb1a6d0e60ddec39538d068bd991c5286830ff870 (patch)
tree62ab564af989b6f1cf91c10cfe1f4e9fd3e908d9 /review-code
parent255031a403fdfb4ea49938068399270121ed1975 (diff)
downloadrulesets-b1a6d0e60ddec39538d068bd991c5286830ff870.tar.gz
rulesets-b1a6d0e60ddec39538d068bd991c5286830ff870.zip
feat(workflows): promote reusable spec-review checks from emacs-d review passes
I folded the reusable, product-neutral checks from two emacs-d review passes into the canonical spec-review.org, so they survive the startup rsync and reach every project instead of living only in a downstream copy. The additions cover package-readiness and Makefile scope, actionable error strings, observability and diagnostics, long-running performance and failure-mode research, defcustom surface, a documentation plan, architecture weak-point mitigation, simplicity controls, extension/plugin developer experience, comparable-product sentiment, terminal-state discovery, CLI-wrapper value, and rollout/rollback, plus three reviewer principles and a generalizable-question harvesting rule. The promotion is a pure superset. Every change adds or expands a generic check, nothing regresses. Project-specific findings stayed in the source spec. The handoff that asked for this is preserved under docs/design.
Diffstat (limited to 'review-code')
0 files changed, 0 insertions, 0 deletions