A guide for creating a GitHub Pull Request, which is a request to merge code changes into another branch. It covers choosing the target branch, following the repository's template, and using the expected title format.
A guide for addressing problems found during code review, which is the process of checking proposed changes before they are merged. It organizes feedback by severity and requires verification after fixes.
A guide for rewriting GitHub Issue or Pull Request titles in Conventional Commits format, such as type(scope): subject. It uses the issue or PR details and code changes to infer the title.
A code-review assistant that examines the implementation of a development task and writes a review report. It expects task files and the code changes to be present in the workspace.
A workflow for posting task progress as a comment on the related GitHub pull request. A pull request is a proposed code change that others can review before it is merged.
A procedure for running integration tests in the FIT Framework. Integration tests check that multiple parts work together by starting the service and calling its interfaces.
An automated test process for the FIT Framework that builds the project, runs tests, starts the service, and checks its health and Swagger documentation.
A command for closing a GitHub Code Scanning alert, which is a notice that automated security checks found a possible problem in code. It shows the alert and records a user-confirmed reason before closing it.
A Git commit command that reviews local changes, checks files before editing, and creates a commit with a suitable message. It can also hand off to commands that push changes and open a pull request.
A task-closing workflow that marks a finished task as complete and moves its records into a completed folder for archiving. Archiving means keeping finished work separate from active work.