▄████▄ ▄ ▄█████ ██ ▄█▀ ██ ██ ██ ▄█████
██▄▄██ ▄▄█▄▄ ▀▀▀▄▄▄ ████ ██ ██ ██ ▀▀▀▄▄▄
██ ██ █ █████▀ ██ ▀█▄ ██ ██████ ██████ █████▀
Agent skills for shipping changes with care: a ship gate before every commit or pull request, a second opinion from a different model, audits that become issues, stacked pull requests, and Gherkin scenarios for every bug. They work in Claude Code, Codex, Cursor, OpenCode and Pi.
/plugin marketplace add andeeplus/aplus
/plugin install aplus@andeeplus
Send them as two separate prompts. The skills are then available as aplus:<skill>.
codex plugin marketplace add andeeplus/aplus
codex plugin add aplus@andeeplusAdd the plugin to opencode.json. OpenCode installs it from GitHub at startup.
{ "plugin": ["github:andeeplus/aplus"] }OpenCode 2 reads the same entry under plugins.
pi install git:github.com/andeeplus/aplusCursor has no install command for a plugin from GitHub. Use one of these:
-
For yourself: clone the repository into Cursor's local plugins folder, then run Developer: Reload Window. The skills appear under Customize. Pull the clone to update.
git clone https://github.com/andeeplus/aplus ~/.cursor/plugins/local/aplusOn Teams and Enterprise, an admin must turn on Allow Local Plugin Imports.
-
For a team (Teams and Enterprise): in the Cursor dashboard, open Plugins & MCPs, select Add Marketplace, then Import from Repo with
https://github.com/andeeplus/aplus.
The skills are generic: they never name a project's commands, branches or paths. They read those from the project:
| File | Holds |
|---|---|
AGENTS.md at the repository root |
Coding rules, the integration branch, the merge method, issue and pull request policy |
A project skill that AGENTS.md names, such as .agents/skills/<project>/SKILL.md |
A table pointing each need (checks, CI, test setup, release notes, issue forms) to the file that holds it |
.github/ |
Issue forms, labels.yml and the pull request template. The github skill's --init installs default forms and labels. |
The skills chain into one flow. Each step names the skill that runs it, and each skill hands over to the next. deliver runs the whole flow for an idea, a ticket or a program of issues.
- Decide. triage checks a ticket is real, finds where it lives and recommends bug, misuse or request. audit does the same for a whole area of code.
- Plan. define turns an idea or a ticket into a spec: scope, the code it touches, acceptance scenarios and open decisions. create-issue turns the decision or the spec into an issue that stands alone, or an ordered program of them. gherkin writes the expected behaviour as scenarios.
- Build. debug proves a bug's root cause with a failing loop. testing picks the test layer and writes the test that fails first.
- Gate. final-review runs the checks and three parallel reviews, fixes the easy findings once, then asks second-opinion for another model's view. It ends with
ready to shipornot ready. - Ship. commit-expert writes the commits and release note. create-pr opens one PR per issue, stacks dependent work, answers reviews and merges when asked.
- Pause. handoff writes a note a fresh agent can resume from.
github and atlassian run the host commands for steps 2 and 5.
| Skill | Use |
|---|---|
| commit-expert | Commit messages, PR titles, changelog lines and release notes; splitting work into commits |
| senior-technical-writer | Writing and reviewing docs against the code they describe |
| testing | Choosing a test layer and writing tests that can fail |
| gherkin | Given/When/Then scenarios: every bug's expected behaviour, acceptance criteria, Cucumber feature files |
| second-opinion | A different agent and model reviews a finished change, read-only, in at most three rounds |
| final-review | Ship gate: checks, three parallel reviews, one fix round, a second opinion, a ready or not-ready verdict |
| create-issue | Issues that stand alone: duplicate check, problem and evidence first, programs of ordered issues |
| create-pr | Open pull requests: one per issue, dependent work stacked, reviews answered, merged only when asked |
| atlassian | Bitbucket pull requests and pipelines, Jira issues, Confluence pages, through atlassian-cli |
| github | Issues from validated draft files, pull requests and stacks with gh-stack, checks and reviews through gh |
| audit | Audit an area into local notes, turn findings into issues, carry them through to merged PRs |
| deliver | Take an idea, a ticket or a program of issues to pull requests ready to merge, running the other skills in order |
| define | Turn an idea or a ticket into a spec: problem, scope, code touched, Gherkin acceptance, open decisions |
| triage | Decide what to do with a ticket: is it real, where does it live, bug, misuse or request |
| debug | Find a bug's root cause with a loop that fails, then fix it behind a regression test |
| handoff | Pause work into a note a fresh agent can resume from |
| code-quality | Strict maintainability check of the current branch's changes; final-review's code-quality reviewer |
Merging a change with a changeset to main opens or updates a release PR; merging that PR tags the version. CHANGELOG.md records what changes in each release.
MIT. Vendored files keep their own license beside them.