Skip to content

Pattern quality: Replace unactionable code-improvement tip with scoping guidance #258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 1 commit into from
Sep 5, 2026
Merged

Pattern quality: Replace unactionable code-improvement tip with scoping guidance #258

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion patterns/archetypes/code-improvement.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@
"tips": [
"Use schedule triggers for continuous maintenance coverage",
"Add pre-steps to run tests/linters before the agent starts \u2014 validates baseline",
"Avoid pr-fix and ci-doctor templates \u2014 both have <20% success in practice",
"Scope each run to one narrow, well-defined improvement (a single failing check or a named category of fix) rather than an open-ended \"fix anything broken\" mandate \u2014 broad, unscoped code-improvement workflows have the lowest observed success rates",
"Use explicit DO NOT constraints to keep changes scoped to the requested improvement",
"Use protected-files: fallback-to-issue for manifests, CI configuration, and agent instructions",
"Add a pre-activation step that skips scheduled runs once too many open PRs share your title prefix, to avoid spamming maintainers"
Expand Down
2 changes: 1 addition & 1 deletion scripts/generate-patterns.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ def classify(wf):
"tips": [
"Use schedule triggers for continuous maintenance coverage",
"Add pre-steps to run tests/linters before the agent starts — validates baseline",
"Avoid pr-fix and ci-doctor templates — both have <20% success in practice",
"Scope each run to one narrow, well-defined improvement (a single failing check or a named category of fix) rather than an open-ended \"fix anything broken\" mandate — broad, unscoped code-improvement workflows have the lowest observed success rates",
"Use explicit DO NOT constraints to keep changes scoped to the requested improvement",
"Use protected-files: fallback-to-issue for manifests, CI configuration, and agent instructions",
"Add a pre-activation step that skips scheduled runs once too many open PRs share your title prefix, to avoid spamming maintainers",
Expand Down
Loading