codagent

Plugin codagent from marketplace codagent in Codagent-AI/agent-skills. Commands read from the repo's manifest — 17 days ago.

Skills (27)

• release

  Creates a release PR from merged PRs — gathers merged PRs since last tag (plus any unmerged current-branch PR), calculates semver bump from conventional commit titles, generates changelog entries, and opens a release PR. Works from any branch: includes both main and current branch changes. Activates

• ask-questions

  How to ask users questions interactively: which tool to use, how to batch questions, and when to ask serially. Follow this skill when asking clarifying questions, requesting confirmation, collecting missing requirements, or pausing for user input. Invoked by other skills rather than directly by the

• call-agent

  Safely invokes one Runner-owned child agent with a complete standalone prompt, independently verifies its findings, and reports results without hiding failures or disagreements. Use when a workflow or caller asks to use codagent:call-agent, call the Runner-owned call_agent tool, obtain an independen

• design

  Creates design artifacts through collaborative brainstorming of approaches, architecture, and trade-offs. Use when the user says "design this", "create a design", "brainstorm approaches", or "write a design doc".

• finalize-pr

  Orchestrates the full post-implementation loop: push PR → wait for CI → fix failures → repeat until CI passes or termination rules trigger a pause. This skill should be used when the user says "ship it", "finalize pr", "push and fix CI", "push pr and wait for CI", or invokes "codagent:finalize-pr".

• fix-pr

  Fixes CI failures and review comments on the current branch's pull request by dispatching a fixer subagent, verifying with the validator, and pushing the fix. Use when the user says "fix pr", "fix CI failures", "address review comments", or invokes "codagent:fix-pr".

• handoff

  Summarizes a specific aspect of the current conversation so another agent can resume. Use when the user says "handoff", "summarize for handoff", "write a handoff", or wants to capture context for another agent session. The user MUST specify what aspect to summarize in their prompt (e.g., "handoff th

• implement-change

  Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

• init

  Initializes Agent Skills in a project by checking prerequisites and verifying the validator configuration. Use when the user says "init", "set up agent-skills", or "initialize agent-skills".

• orchestrate-change

  Implements a well-specified change (approved change artifacts, specs, or similar) as an orchestrator that delegates all code changes to sub-agents. Use by default when implementing any well-specified change, unless instructed otherwise.

• plan-tasks

  Creates a structured implementation task breakdown for a structured change, synthesizing proposal, design, specs, and any supplied test-plan obligations into self-contained per-task files; use when the tasks artifact is the next step in a change.

• prepare-acceptance

  Explores an implemented change to find defects its green test suite missed, exercises every user-visible requirement the change adds or modifies at least once, sizes further exploration to what actually changed, reports findings without fixing them, waits for current-head CI, and prepares evidence f

• proposal-review

  Adversarial review of a proposal — challenges the why, what, and how, and suggests concrete alternatives. Use when asked to review a proposal, challenge an idea, stress-test an approach, or provide a devil's advocate perspective before specs or design are written.

• propose

  Evaluate whether a software idea is worth building, then write the proposal document. Use when the user wants to assess an idea, says "evaluate", "propose", "is this worth building", or "should we build". If the idea passes evaluation, write the proposal document using the provided template.

• push-pr

  Commits changes, pushes to remote, and creates or updates a pull request for the current branch. Use when the user says "push pr", "create pr", "push and create pr", or invokes "codagent:push-pr".

• review-approach

  Performs the final review of a completed proposal, product specification, technical design, and test plan for cross-artifact consistency, consequential gaps, missing decisions, weak tradeoffs, failure modes, testing strategy, and better alternatives; use when asked to review an approach, challenge d

• review-assumptions

  Reviews risky/notable assumptions and context gaps surfaced by implementor session reports, fixes high-confidence issues directly, and asks one clarifying question at a time for ambiguous findings. Use when the user says "review assumptions", "audit implementor assumptions", or when invoked by a wor

• review-spec

  Reviews proposal, specification, design, and task artifacts for internal consistency, testability, traceability, and cross-artifact alignment. Use when asked to review a spec, review artifacts, check design documents, check a change for consistency, or verify artifact quality before implementation.

• review-tasks

  Reviews an implementation task plan against its approved proposal, specifications, design, and test plan, finding only defects that can be corrected in the task files; use when asked to review tasks, review an implementation plan, verify task and automated-test coverage, or check whether a task brea

• session-report

  Audits your session for assumptions and context gaps — things only a human can act on. Use when the user says "session report", "review assumptions", "what did you struggle with", "audit your session", or wants a retrospective on execution quality.

• simple-plan

  Lightweight planning for small, quick changes. Combines propose, spec, and (optionally) design into one conversational pass, then writes tasks.md so the change is ready for implementation. Activates when users ask for "simple plan", "quick plan", "plan this", or "planning mode" for a change that doe

• spec

  Drives interactive requirement discovery to produce spec files. Use when the user says "spec this", "write specs", "create specs", or "run the spec skill".

• task-compliance

  Review an implementation against task file requirements. Checks every spec scenario and Done When criterion, identifies gaps, and reports them. Use when the user says "task compliance", "check compliance", "review against the task", or to verify implementation completeness before shipping.

• test-flows

  Exercises a small or branch-local software change through representative public user or client flows and reports concise observed evidence, defects, ambiguities, and limitations without fixing code, running automated suites, requiring a PR, or preparing formal acceptance; use for lightweight manual-

• test-plan

  Collaboratively creates a risk-based test plan for a defined software change using the automated test pyramid plus the envelope an exploratory acceptance pass runs under and exceptional human-only testing; use after specifications and design are complete, when asked to plan testing, define integrati

• verify-behavior

  Plans how to verify each behavior in a change's spec, then records evidence that each check passed. Use when asked to plan or record verification of a change's behavior, or to invoke codagent:verify-behavior.

• wait-ci

  Polls CI check status for the current branch's pull request and reports pass/fail/pending/comments, surfacing PR review comments even when CI is green. Use when the user says "wait for CI", "check CI", "poll CI", or invokes "codagent:wait-ci".

Similar plugins