microsoft/amplifier-app-opencode.
3 skills★ 3View on GitHub ↗
- 100/100
amplifier-opencode-bugfix
Triage and fix an amplifier-app-opencode bug, from report to verified fix, using E2E-test-driven development. Covers intake, ruling out non-code causes (stale server, stale install, mismatched floor), root-cause pinning, the coverage-gap gate that classifies why e2e missed it, red/green regression TDD, and scoped verification. Stops before release.
- 100/100
amplifier-opencode-new-feature
Develop a new amplifier-app-opencode feature from ideation to working end-to-end in a DTU, using E2E-test-driven development with the spec landing in the same commit as the contract change. Covers orientation, planning, spec-first review, red/green E2E TDD, and the loop-until-green discipline. Stops before release.
- 100/100
amplifier-opencode-release
Release amplifier-app-opencode: bound the commit range, sweep the diff for anything that should not ship, bump both version declarations in agreement, write the changelog, confirm the agent-version floor decision, run the local gate, and open the release PR. Merging to main IS the release; there is no tag or publish step.