‹ Back to apps
docspring-agent-playbook
DocSpring's engineering principles, AGENTS.md templates and six workflow skills (ticket kickoff, PR review, second-opinion review, fix CI, browser QA, session wrap-up) for Claude Code, Codex and other agents.
What’s inside
6 skills- Skillfix-ciPushes the current branch, waits for the whole CI pipeline, then fixes every failing job and every valid pull request review comment (from people or review bots) locally as one batch, pushes once, replies to each review thread and resolves the ones its fixes address, and repeats until CI is green with no open threads it can settle. GitHub and GitHub Actions are the worked adapter; other providers need their commands in the settings. Use when the user asks to "fix CI", "get CI green", "get the checks passing", "wait for CI and fix it", "address the review comments" or "resolve the PR comments" on the current branch. Not for reviewing someone else's PR (use your review process) or for an independent second review (second-opinion-review).
- Skillpr-reviewCollaborative pull request review with a persistent review folder, independent read-only investigations of bounded focus areas, evidence-backed findings that the user adjudicates one by one, and review comments posted only after the user approves their exact text. Covers someone else's PR and a self-review of your own branch before you open one, and resumes a review after new commits without starting over. Use when the user says "review PR 123", "review this branch", "self-review before I open the PR", "continue the review", "discuss the findings" or "draft the review comments". Not for an unattended review by another model (second-opinion-review) or for fixing failing CI and review comments (fix-ci).
- Skillsecond-opinion-reviewRuns an independent second code review of a committed branch or pull request with another agent's CLI (the Codex CLI is the worked example) unattended in the background. It keeps the second reviewer away from the first reviewer's notes, checks that it left the repository unchanged, then verifies each of its findings against the code before presenting them. Use when the user asks for a second opinion, an independent or impartial review, another model's review, "get Codex to review this", or before pushing a critical fix or a change that needs a careful review. Not for doing your own review of a PR (pr-review) or for fixing failing CI and review comments (fix-ci).
- Skillsession-wrap-upSweeps a working session for loose ends before it closes. Re-reads the saved transcript from disk (Claude Code and Codex formats, including everything before a context compaction), subagent reports, review notes, the PR and the diff, lists every item that was raised but not resolved, checks the tracker for duplicates, and proposes one list with a disposition per item (fix now, ticket with a reason, comment on an existing ticket, save as a rule, drop with a reason). Acts only on what the user approves, then cleans up leftovers and a merged branch's worktree safely. Use when the user says "wrap up", "wrap up the session", "any loose ends?", "anything not in the tracker yet?", "what did we leave unfinished?", or after a feature ships. Not for reviewing a diff for bugs (use your review process).
- Skillstory-kickoffInvestigates a ticket before any code is written. Has a short path for mechanical changes. Otherwise records the exact code it investigates, checks the ticket's claims against the code, maps callers, existing data and the behavior other code, clients and customers rely on with bounded read-only investigators, then writes a plan whose regression tests each state how they fail on the parent commit and which marks only real judgment calls for the user. Builds test-first, checks the result against every recorded decision before the PR, hands off to the team's review process, and turns what that review found into new lessons. Use when the user says "start work on ENG-123", "pick up this issue", "let's do this ticket", "work on #42", "plan this before building it" or "investigate before coding". Not for reviewing a branch or PR that already exists (pr-review or second-opinion-review).
- Skillui-qa-passRuns a branch's app locally and drives a headless browser through the screens the change touches, choosing the states, themes, widths and roles by what the change could break. Takes a screenshot of each, fixes bugs and obvious polish as it goes with before and after shots, and writes a report that leads with the decisions the user needs to make. Use when the user says "QA this", "do a QA pass", "click through every changed screen", "screenshot every state", "test it in a browser and make a report", or before asking for review of a change people can see (app screens, marketing or docs pages, emails). Not for writing or fixing the automated browser test suite.