Skip to content

Add a create-pr skill for pfe projects#49

Open
seb4stien wants to merge 6 commits into
mainfrom
feat/pfe-create-pr
Open

Add a create-pr skill for pfe projects#49
seb4stien wants to merge 6 commits into
mainfrom
feat/pfe-create-pr

Conversation

@seb4stien

Copy link
Copy Markdown
Contributor

@seb4stien seb4stien requested a review from a team as a code owner June 17, 2026 15:00
---
name: create-pr
description: Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
# reference documentation: https://github.com/canonical/platform-engineering-docs/edit/main/docs/delivery-workflows/github/pull-requests/index.rst

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure of the efficiency or impact of placing reference documentation in the skill's description. I think it might be better if we reference in the body directly. WDYT?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's for us, not for the agent :)
The content is copy-pasted in the body. We can remove it if you think it will introduce noise.

Comment thread groups/platform-engineering/skills/create-pr/SKILL.md
- The reason the change is needed
- Any additional information requested in the pull request template.

Use the template available in `.github/pull_request_template.md>` if available.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think of adding an additional suggestion to include key agentic resource usage metrics if available?
Or should we add that to the template?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would go for the template indeed, easier to test :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants