القائمة
Work instruction for concluding a feature. If you helping with development in ANY way, you MUST load this skill.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill described the process to follow when asking the user questions. If you will ask the user questions in any way, load this skill first.
Guidance on how code should be written in this repo. If you add or modify code, load this skill.
This skill defines the process to follow for developing new features. Load this skill if you are tasked with changing anything in the `src/myteam/` directory.
Load this skill only when asked to by the user.
This skill describes our philosophy towards the kinds of tests we write and the framework used to implement tests. If you need to read, add, or modify tests, load this skill.
Local development-workflow guidance for asking the user questions. Load this skill before any development-workflow role asks the user questions or requests approval.
| name | Conclude Feature |
| description | Work instruction for concluding a feature. If you helping with development in ANY way, you MUST load this skill. |
Before a feature branch is ready to merge, the following must be complete.
code-linterPlease delegate to the code-linter role. Address any concerns they raise.
After addressing their concerns, run it again. Loop until no concerns are raised.
Do not proceed until this step is complete.
project-myteam-updatePlease delegate to the project-myteam-update role.
When they are finished, proceed.
Do not proceed until this step is complete.
If any changes have been made by this point, please commit them.
Follow guidance in the git-commit skill.
If any code or templates have changed, then the version in pyproject.toml needs to change.
Because we are still in preview, the leading version will stay at 0. If the public interface has a breaking change, the minor version should increase. If the public interface has no breaking changes, just the patch version should increase.
Please describe the scope of the changes in the current branch and determine what version bump is needed. Then inspect the version:
Only one version bump in a branch is needed. If the version in the branch has already been bumped, do not bump it again.
Do not decide this from the current file contents alone. Check the branch history first to see whether this branch already includes a version-bump commit or a prior change to the version/changelog files. Compare against the branch's earlier commits or merge-base as needed before making any new bump. If the branch already contains a version bump, keep that version unless the user explicitly asks to change it.
Please update the changelog to include a helpful description of the changes made.
The Readme and other documentation (if relevant) must be up-to-date. Inspect the code changes and update the documentation accordingly.
If the feature branch completes one or more backlog items, move those backlog documents from
src/governing_docs/backlog/ into src/governing_docs/backlog/completed/.
Only move backlog docs that are clearly complete from shipped behavior in the branch.
Commit any additional changes.