athena

Plugin athena from marketplace Athena in HomericIntelligence/Athena. Commands read from the repo's manifest — yesterday.

Skills (19)

• address-review

  Address every review thread on a pull request. Use this skill when a PR has review comments. For each thread, fix the concern in code, reply on the thread, and resolve it. Handle a dirty worktree, a stale branch, and conflicts yourself.

• advise

  Retrieve relevant Mnemosyne guidance from the available local checkout and open pull requests before unfamiliar planning or implementation. Stale, missing, or unverifiable knowledge limits the advice but does not stop the primary task.

• babysit

  Coordinate a set of long-lived agent sessions and automation loops to a completion boundary. Use this skill when the user asks you to watch, track, revive, babysit, or guide many agent sessions, when sessions or hephaestus-automation-loop runs do work that does not appear in commits or pull requests

• brainstorm

  Use before complex creative work. Examine intent and requirements. Use available Mnemosyne advice; missing guidance does not stop otherwise authorized work.

• change-review

  Review one change instance. Inspect available input, report the judgement, and proceed without requiring attestation.

• finalize-plan

  Create an issue body after `plan-issue` and `issue-review` deliver their results. `--draft` is read-only. Preserve foreign comments. Missing cleanup capability does not block an authorized body update.

• git-worktrees

  Prepare an isolated feature worktree under the primary project’s ignored .worktrees directory. Preserve existing checkouts and changes. Record baseline failures and continue authorized work.

• implement

  Implement one approved plan for a GitHub issue in the current worktree. Use this skill when an issue has a plan and the next step is code, tests, a commit, and a pushed branch. Handle a dirty worktree, a stale branch, and conflicts yourself.

• issue-review

  Use before implementation to review a GitHub or GitLab issue and its current plan. Check architecture, scope, risk, and behavior-first verification. Use `--report-only` for read-only work. Delivers the review as a comment and sets the matching state label from the verdict.

• learn

  Preserve a Mnemosyne lesson that the source supports. Discovery compares merged skills and open pull requests, is best effort, and can use a stale checkout. Specificity is not a rejection reason when a case adds a reusable decision branch. A durable write uses an isolated worktree and pull request.

• myrmidon-swarm

  Coordinate complex work with dependency-aware subagents in isolated worktrees. Use sequential work if the host cannot delegate. Use available Mnemosyne advice; missing guidance does not stop otherwise authorized work.

• plan-issue

  Draft or publish one implementation plan for a GitHub or GitLab issue. Use this skill after architecture and knowledge review when an issue needs an executable, behavior-first plan. The `--draft` mode is read-only.

• pr-review

  Review one implementation instance. Post the review, set the latest implementation verdict label, and preserve secret and PII protection.

• realign

  Find evidence-backed architecture drift and code anti-patterns. Repair supported candidates within existing task authority. Keep candidate IDs for tracking. Refresh changed evidence and preserve existing work. AISlop is optional. Run native validation and report gaps without blocking independent pre

• repo-review

  Review one repository instance and return actionable findings and judgement.

• simplify

  Review a repository or target path for safe deletion, reuse, consolidation, or retention when subtraction may satisfy the current requirement with less code or less system complexity. Use this skill for read-only review. Recover missing bindings and continue in batches. Report remaining coverage gap

• systematic-debugging

  Investigate root cause before you repair a bug or unexpected behavior. Use available Mnemosyne advice; missing guidance does not stop otherwise authorized work.

• test-driven-development

  Use this skill before you write implementation code for a feature or bug fix. Use RED-GREEN-REFACTOR as the strong default. Record justified exceptions and alternative verification. Preserve good implementation that predates a test.

• tidy

  Clean up unused repository branches and worktrees through the dependency-locked Hephaestus tidy command. Use this skill only for unused branch and worktree cleanup, not for general rebase requests or rebases of active worktrees. Recover dependency or capability failures and provide exact manual comm

Similar plugins