← all publishers

Practical-Office

@practical-office source repo

Report this profile Claim this profile

• 11 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Review · practical-office

   Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
   0 installs
2. ▌
   To Prd · practical-office

   Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
   0 installs
3. ▌
   Triage · practical-office bundle

   Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
   0 installs
4. ▌
   Create Pr · practical-office

   Creates a GitHub pull request using gh CLI: gathers git status and diff vs base, pushes branch, and opens PR with Summary and Test plan. Use when the user asks to create a PR, open a pull request, or submit changes for review.
   0 installs
5. ▌
   Pr Review · practical-office bundle

   PR-Review: gate GitHub pull requests — inspect CI and diff, approve or request changes, then squash-merge only when the gate is green. On REQUEST_CHANGES or any hold, always write Why (lens + evidence) and Next steps (author-actionable) on the GitHub review and in the chat report. Use when the user wants to review and merge a PR, batch-review PRs, re-review after changes requested, or run a CODEOWNER merge pass (especially Book-IQ/frs).
   0 installs
6. ▌
   To Issues · practical-office

   Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
   0 installs
7. ▌
   Task Handoff · practical-office

   Produces a structured handoff document for the next agent or developer with goal, progress, next steps, risks, files touched, and test plan. Use when ending a session, switching agents, pausing work, or when the user asks for a handoff, status summary, or context transfer.
   0 installs
8. ▌
   Release Readiness · practical-office

   Pre-merge release checklist covering tests, docs, rollback, security, and breaking changes. Use before merging to main, cutting a release, or when the user asks if a branch is ready to ship.
   0 installs
9. ▌
   Security Secrets Check · practical-office

   Scans staged changes and diffs for leaked secrets, API keys, tokens, and credentials before commit or PR. Use when preparing commits, opening pull requests, reviewing diffs, or when the user mentions secrets, tokens, .env files, or credential leaks.
   0 installs
10. ▌
    Tenant Isolation Check · practical-office

    Reviews multi-tenant backend changes for tenant context enforcement, no cross-tenant data access, and no primary-tenant fallback. Use when working on tenant-scoped APIs, database queries, auth middleware, or when the user mentions multi-tenancy, tenant isolation, or tenant headers.
    0 installs
11. ▌
    Setup Practical AI Skills · practical-office bundle

    Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so Practical Office engineering skills know this repo's issue tracker (GitHub default), triage label vocabulary, and domain doc layout. Run once per application repo before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out`.
    0 installs