Verify code implementation against change specifications and architectural constraints.
npx skills add https://github.com/eavichay/mycli --skill change-verify
Please help me install this Agent Skill. Skill: change-verify Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/change-verify Command: npx skills add https://github.com/eavichay/mycli --skill change-verify
This Skill addresses the risk of incomplete or non-compliant code changes by enforcing a rigorous verification process against defined success criteria and architectural constraints.
Invoke the change-verify skill to validate the current implementation against the requirements defined in the active change specification file.
High-intent search queries and answers about installing and using this skill.
Verifying code implementation against project specifications involves validating completed code changes against functional requirements and success criteria defined in change specification files. This ensures the implementation meets all architectural constraints.
Governance enforcement works by integrating with project-level constitution files to ensure all code changes adhere to established architectural principles. This validates functional requirements before changes are approved.
Yes, you need change specification files and project-level constitution documents to perform code verification. The validation process requires access to these governance documents to update verification status and check compliance.
Automated verification of code changes is the process of validating implementation completeness against specific success criteria and functional requirements defined in change specifications. It operates within a repository-wide specification framework.
Yes, you can automate environment setup and cleanup during specification verification by executing pre- and post-verification hooks. These hooks integrate into the workflow to handle environment tasks around the validation process.
You should avoid using automated specification verification when change specification files or project-level constitution documents are not available, as the validation process requires access to these governance documents to function properly.
chrislawcodesGenerate structured feature specification documents in Markdown format.
p-potvinExecute validated Azure deployment workflows using azd, terraform, and native commands.
aberrantCodeAutomates OWASP-aligned security checks, secrets management, and dependency audits for software projects.
levnikolaevichRun project test suites across frameworks and output verdict JSON.
