solve-issue-local

To resolve build and test issues, follow a standardized workflow that targets Java Maven builds and Python pytest commands, ensuring changes pass linting and tests before creating a PR.

The best way to structure a PR for issue resolution is to apply a standardized build, test, and review workflow, followed by a post-implementation checklist to verify changes are complete and documented.

Yes, mage-bench development scenarios require YAML frontmatter with name and description at the skill root, alongside a structured description and a folded metadata block for discovery tooling.

Yes, the issue resolution workflow includes linting and code review checks, providing targeted commands to verify changes and a checklist to ensure all modifications are well-documented.

Yes, you can use this workflow for documentation updates in mage-bench, as it mandates a structured description and post-implementation safety checks to ensure changes are complete.

Safety checks for discovery tooling are needed to validate the required YAML frontmatter and folded metadata block, ensuring the skill root is properly structured for automated discovery.