mahsanamin

Record an improvement, learning, fix, or refinement to the Agentic Repos framework. Invoke when a new pattern emerges, a bug is found in a skill/agent/rule, or a workflow refinement is identified during work. Handles version bumping, CHANGELOG updates, and cross-file consistency. Also user-invocable via "ar-add-improvement" or "update framework".

Install or update context-processing skills (discussion, email, meeting, specs, state) into a Docs Project. Separate from ar-taskflow - does not touch ar-taskflow skills or config.

Adopt Agentic Repos in a project, writing its per-repo config + rules layer by extracting the codebase's real conventions. Say "ar-install" or "make this repo agent-ready".

Install or refresh the global Agentic Repos layer on this machine (ar-* skills, scripts, session hook, default-branch guard). Say "ar-install-tools" or "setup tools".

Reviews a PULL REQUEST of the Agentic Repos framework SOURCE repo itself for project-based noise. Its input is a framework PR, on trigger it FIRST asks which agentic-repos PR to review (framework PRs only; it refuses PRs from any other repo). Proves the PR introduces ZERO project-based noise into the project-agnostic framework, installed artifacts (rules/, skills/, agents/, templates/, setup.md) AND docs/. Catches a source project's identity (real names, packages, developer paths, tickets, people, dated incident notes), whole files bound to one project (a <project>-feedback.md mining doc, anything named after or dominated by a single product line, these belong in the source project, not the framework), stack idioms leaking into stack-agnostic skill/agent bodies, ungenericized business-domain examples, rationale/version-history bloat, mis-tiered rules, and version-file drift. Use whenever you want to review/self-review an agentic-repos PR for "does this leak or bind a project into the generic framework," befor

Refresh an adopted project's per-repo config + rules layer to the current framework version. Say "ar-upgrade" or "refresh the project rules".

Assess how agent-ready a repository is and raise it. Reads the actual codebase, extracts its real conventions into rule files, wires the config seam, and reports a readiness scorecard. Say "ar-agent-ready", "make this repo agent-ready", or "extract the rules for this project".

Audit what the code ASSUMES against what production ACTUALLY does, using Datadog traces, and turn mismatches into fix tickets. Say "ar-api-dd-compare" or "trace audit". On-demand only (Datadog MCP is interactively authenticated).

Review one or more GitHub PRs in an isolated git worktree using parallel agents, without disturbing the working repo. Local routine: for each PR it creates a dedicated review worktree on a review-pr-<N> branch (never your own working branch), runs the project's PR-review skill, optionally auto-posts the comments that clear a high bar, then tears the review worktree down. Use when asked to review a PR, review my assigned PRs, do a worktree PR review, or when a scheduled "PR review" routine fires. Parameterized: pass repo (full local clone path for unattended runs), pr (a number, a list, or "mine" = all PRs assigned to me), and optionally the review skill, parallelism, cleanup, and post (auto = post the comments that clear a high bar without asking, THE DEFAULT; draft = review only, post nothing). Invoke as `run a_r_l_pr_review for repo=<path> pr=<number|mine>`. Triggers even without the exact name: "review PR 123 in a worktree", "review the PRs assigned to me", "do an isolated review of this PR".

Review a GitHub PR end-to-end from just its URL. Give it a PR link (or owner/repo#N); it finds the repo you ALREADY have cloned locally (via a cached lookup, then a scan of your cd_w workspace — never a duplicate clone), clones into cd_w only if you don't have it, spins up a git worktree checked out on the PR's real head branch updated to latest, then runs the project's own review skill (review-pr) if it has one or the global global-pr-reviewer otherwise, auto-posts the comments that clear a high bar as GitHub inline review comments, and tears the worktree + local branch down. This is a SKILL, not a routine (no _r); a routine may call it. Use when asked to "review this PR <url>", "review a PR from its link", "do a full review of <github pull url>", or given a bare GitHub PR URL to review. Parameterized: pr (URL / owner/repo#N / number), post (auto | draft), reviewer (auto | project | global).

Unattended QA routine that smoke-tests a web flow on STAGING and files ONLY confirmed, reproducible bugs to a Jira epic. Local routine: it reuses the signed-in browser session, drives a named flow skill end-to-end on desktop and mobile viewports, applies a strict settle-and-reproduce verification gate, dedupes against the epic's existing children, and files clean bug tickets. Use when asked to smoke-test / QA a staging flow, hunt for reproducible bugs in a booking or signup funnel, or when a scheduled "staging QA" routine fires. Parameterized: pass flow_skill, base_url, epic, and ticket_creator. Invoke as `run a_r_l_staging_qa_sweep with flow_skill=<skill> base_url=<staging host> epic=<KEY>`. Triggers even without the exact name: "QA the app flow on staging and file bugs", "smoke test the booking funnel", "find reproducible defects on staging".

Create a clean, human-readable git commit for the current changes. Groups the diff into a coherent commit, writes a clear message in the project's style, and commits (respecting the repo's permission posture). Say "a_sk_commit" or "commit" when ready to commit. Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

Open a GitHub pull request for the current branch, filling the project's PR template properly. Pushes the branch if needed, fills the template body from the actual changes, picks the correct base branch, and creates the PR (respecting the repo's permission posture). Say "a_sk_pr" or "pr" when ready to open a PR. Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

Drive test coverage on the current change up to the project's SonarQube (or CI) coverage gate. Finds the coverage command, measures coverage on the changed/new code, writes tests following the project's testing conventions for the uncovered lines, and re-runs until the gate passes. Say "a_sk_sonarqube_coverage", "raise coverage to the gate", or "get coverage green". Generic and project-agnostic — imported from an upstream framework and de-coupled from it.

Write professional work messages (Slack, email, escalations, status updates) from the standpoint of a VP of Engineering / VP R&D. Use when the user asks to draft, rewrite, sharpen, or "make this sound better" for a message to colleagues, managers, clients, or cross-team threads, especially under deadline pressure or conflict. Protects delivery teams, makes trade-offs visible, stays factual and non-defensive.

Turn a rough, half-formed task description into a clean, self-contained instruction prompt for an autonomous or scheduled routine (Claude Code local/cloud routine, /goal, /loop, /schedule, or a reusable skill). Vets the raw text, fixes typos and ambiguity, clarifies only the decisions that change the steps, verifies the plan against a prior real run when a reference exists (a PR, a past routine, a transcript), and hardens the result for unattended execution. Use when the user says "write this routine instruction", "make this prompt count", "clean up this prompt so Claude does it right", pastes a draft for a scheduled/local routine, or asks to author instructions for a recurring/automated task.

Implement mdnest features/improvements from the backlog. Read the items in the mdnest brain (MyProjects/mdNest/Features), pick what to build, then implement them one by one — each on its own branch from develop, verified and merged straight into develop (no per-unit PR) — and finish with one clean release PR built on top of main. Say "/md-add-improvement". (Part of the md-* mdnest skill family alongside md-fix-bugs and md-ship.)

Fix the mdnest bug backlog. Read the bugs from the mdnest brain (MyProjects/mdNest/Bugs), judge what's actually a bug (some are already fixed), then fix them one by one — each on its own branch from develop, verified and merged STRAIGHT into develop (no per-bug PR) — and finish with one clean release PR built on top of main. Say "/md-fix-bugs". (Part of the md-* mdnest skill family alongside md-add-improvement and md-ship.)

After implementing a feature or fix in mdnest, run this to update CHANGELOG, docs, website, bump version, sync, and rebuild the local dev stack. Say "/md-ship" after completing any code change. (Part of the md-* mdnest skill family alongside md-fix-bugs and md-add-improvement.)

Execute the next unchecked task in tether's task-sequence.md, end to end, following the project rules. Use when the user wants to start or continue building tether ("do the next task", "continue tether", "build M1", "pick up the next task", "start coding tether"). Reads the design and rules, picks the first unchecked task, implements only that task within the pinned stack, gates on its acceptance criteria, then checks it off and reports. Project-scoped to the tether repo.

Default PR-review playbook bundled with prsnooze. Produces tight, actionable, file:line-anchored findings — no prose, no duplicates, no review-meta. Used when the project being reviewed has no `aa-review-pr` / `review-pr` skill of its own.