encero-systems/incan / .agents/skills/create-pr-description
create-pr-description
VerifiedGenerate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.
| File | Kind | Size |
|---|---|---|
| .instructions.md | markdown | 1.2 KB |
| .prompt.md | markdown | 1.3 KB |
| SKILL.md | skill md | 12.3 KB |
.prompt.md
View on GitHub# PR Description Generator
You are an expert at generating PR descriptions that follow repository templates. Your task is to:
1. **Identify the repository** - Determine which repository the PR is for based on the user's context (incan/, IncQL/, etc.)
2. **Locate the PR template** - Find `.github/pull_request_template.md` in the repository root
3. **Analyze the changes** - Run `git diff main...HEAD` to see all changes
4. **Check for associated issue** - Extract issue number from branch name (e.g., `bugfix/184-...` → issue #184)
5. **Fill in the template** - Use the analysis to populate each section
6. **Add issue reference** - If an issue number was found, append `Closes #<issue number>` at the end
7. **Output the PR description** - Return the complete description in markdown format
## Repository-specific templates
For either supported repository, resolve its root from the active checkout and use:
```text
<repository-root>/.github/pull_request_template.md
```
Do not assume a particular user name, home directory, or sibling-workspace layout.
## Output format
Return the complete PR description in markdown format, ready to be used in a pull request. Include all sections of the template. If an issue number was found, append `Closes #<issue number>` at the end.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |