validating-production-quality

Validating production quality

Sequential steps to be followed when using this skill

When validating production quality, follow those steps.

Create the validating-production-quality Execution Checklist (MANDATORY)

• Before executing anything, create a checklist named validating-production-quality Execution Checklist with all steps of these instructions.
• The validating-production-quality Execution Checklist must include all numbered steps explicitly.
• After completing each step of these instructions, mark the item in the validating-production-quality Execution Checklist as completed.
• Do not skip any item.
• If an item cannot be executed, explicitly explain why.
• Never mark the task as completed while any item from the validating-production-quality Execution Checklist remains open.

1. Inform the user

• Always tell the user "SKILL: I am validating production quality" to inform the user that you are running this skill.

2. Fix any potential regression

• Always run all test scenarios.
• Always fix all the failures that you see in the tests output.

For example, in a Python project:

python -m unittest

3. Update documentation

• Always use skill: updating-doc to update the project documentation.

4. Commit all pending modifications

• Always use skill: committing-changes to commit all your changes in the current branch.

5. Sync the branch with its base

• Always use skill: syncing-branch-with-base to make sure the current branch is up-to-date with its base.

6. Remove any merge commit in the current branch

• Always check that there is no merge commit between the current branch and its base.
• If you find any merge commit, then always remove them by rebasing the branch in a linear way, using cli: git rebase, and push again to the GitHub remote using --force-with-lease option.

Example, in case of merge commits found:

git log --oneline --ancestry-path github/main..my_branch
git rebase main
git push github --force-with-lease