docs: clarify branch matching criteria in copilot guide

Update instructions to match branch names and descriptions with file
changes.

Author: estib-vega

.github/copilot-instructions.md

@@ -40,7 +40,7 @@ Follow this instructions when creating a commit plan:
    - Groups are good, but prefer to have smaller commits than larger ones.
    - Granularity is good.
 2. Determine if any branches should be created
-   - If there are any stacks with branches, take a look at the branch names and match them with the file changes.
+   - If there are any stacks with branches, take a look at the branch names and descriptions and match them with the file changes.
    - Create multiple branches if needed. You can tell if multiple branches are needed if the file changes span multiple projects in the monorepo.
 3. Determine the commits
    - For each group of file changes, determine the commit message. Be descriptive and explain what the changes are.