refactor(rules): narrow ambiguity and output guidance
This commit is contained in:
1 parent
847038d1e0
commit
bfd3093776
2 files changed
+5
-1
No files matched your search
@@ -1,7 +1,7 @@
|
||||
rule_file skill_name trigger
|
||||
angular rules-angular Angular component, template, or RxJS/signal work
|
||||
csharp.md rules-csharp C# or .NET implementation, review, or refactoring work
|
||||
decision-rule.md rules-decision-rule evaluating requirements, ambiguous behavior, or technical choices that need a decision
|
||||
decision-rule.md rules-decision-rule unresolved requirements, ambiguous behavior, or a meaningful technical choice
|
||||
definition-of-done.md rules-definition-of-done validating that a task is complete or ready for review
|
||||
git.md rules-git Git operations such as commits, branches, or merges
|
||||
microsoft.md rules-microsoft Microsoft 365, Azure DevOps, or Teams operations
|
||||
|
||||
|
@@ -33,6 +33,10 @@ Project instructions may specialize global defaults, but must not weaken securit
|
||||
* Prefer self-explanatory code and clear names.
|
||||
* Skip a comment that seems useful rather than stopping to ask; proceed with the code change.
|
||||
|
||||
## Tool output
|
||||
|
||||
* Prefer a script's documented summary mode for routine agent runs; keep warnings and failure diagnostics visible. Use detailed output when investigating a failure or when requested.
|
||||
|
||||
## Language
|
||||
|
||||
* Write code and repository-generated user-facing text in English.
|
||||
Reference in new issue
Block a user