refactor: update branching pattern and PR title guidance in documentation

Signed-off-by: Felipe Sayão Lobato Abreu <github@mentordosnerds.com>

Author: coisa

.agents/skills/github-pull-request/references/implementation-loop.md

@@ -7,7 +7,7 @@ Use this loop for each selected issue.
 - Update `main` or the repository's integration branch before branching.
 - Keep branch names stable and descriptive.
 - Prefer the repository convention when one exists.
-- If no repository convention is defined, use a stable pattern such as `issue-123-short-slug`.
+- If no repository convention is defined, use a stable pattern such as `type-of-issue/123-short-slug`.
 
 ## Implementation Boundaries
 

.agents/skills/github-pull-request/references/pr-drafting.md

@@ -41,15 +41,15 @@ Closes #123
 ## Title Guidance
 
 - Follow repository title rules when they exist.
-- For this repository, prefer `[area] Brief description (#123)`.
+- For this repository, prefer `[area] Brief description`.
 - Use the issue number that the PR closes in the title when it is known.
 - Derive `area` from the touched subsystem, command, or package rather than using a generic label.
 
 Examples:
 
-- `[tests] Add command coverage for sync workflow (#42)`
-- `[docs] Document wiki generation flow (#57)`
-- `[command] Add dependency analysis command (#91)`
+- `[tests] Add command coverage for sync workflow`
+- `[docs] Document wiki generation flow`
+- `[command] Add dependency analysis command`
 
 ## Draft vs Ready