full-brief
Skill12 starsChanged 8 months agoMITView on GitHub
Composite command: run /qq:brief and /qq:timeline in parallel, generating a complete PR review package.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- best-practiceSkill
- bootstrapSkill
- briefSkill
- changesSkill
- claude-code-reviewSkill
- claude-plan-reviewSkill
- codex-code-reviewSkill
- codex-plan-reviewSkill
- commit-pushSkill
- depsSkill
- design-researchSkill
- designSkill
- doc-driftSkill
- doc-syncSkill
- doc-tidySkill
- executeSkill
- explainSkill
- goSkill
- grandmaSkill
- planSkill
- post-design-reviewSkill
- recordSkill
- self-reviewSkill
- tech-researchSkill
- testSkill
- timelineSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
No arguments: compare against the default base branch (develop if it exists, else main, else master)
- Distinctive: line 15
Use two parallel agents to execute:
- Distinctive: line 23
All files go to the same directory, sharing the same timestamp:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Arguments: $ARGUMENTS
- No arguments: compare against the default base branch (develop if it exists, else main, else master)
--base <branch>: specify the comparison base branch
Execution Steps
- Obtain a shared timestamp before launching agents, and pass it (with any
--base) to both. - Use two parallel agents to execute:
- Agent 1: follow the complete instructions of
/qq:briefto generate the architecture change document + PR review checklist - Agent 2: follow the complete instructions of
/qq:timelineto generate the commit timeline + phase-grouped review documents
- Agent 1: follow the complete instructions of
- Once both agents complete, (re)generate
REVIEW_GUIDE.mdper/qq:timelinestep 6 so it indexes all four documents, then report the paths.
Output Files
All files go to the same directory, sharing the same timestamp:
Docs/qq/<branch-name>/arch-review_<timestamp>.mdDocs/qq/<branch-name>/pr-review_<timestamp>.mdDocs/qq/<branch-name>/timeline-arch_<timestamp>.mdDocs/qq/<branch-name>/timeline-review_<timestamp>.mdDocs/qq/<branch-name>/REVIEW_GUIDE.md(no timestamp)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.