.claude/skills/step-07-label-advanced/SKILL.md
# step-07-label-advanced ## What it does Labels Axis 4 — Advanced. Derives the Advanced label from Context Scope using a deterministic mapping. ## Prerequisites - Step 06 completed (Context Scope labeled) ## Context > See `docs/axis-4-advanced.md` for the mapping rule and definitions. > See `DOCUMENTATION.md` section 7 (Axis 4) for the rationale. ## Arguments - `id` (required): Task ID ## Instructions ### 1. Recover context Read `task_info.md` — specifically the Context Scope label from s
npx skillsauth add Pepe39/chameleon-pr .claude/skills/step-07-label-advancedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Labels Axis 4 — Advanced. Derives the Advanced label from Context Scope using a deterministic mapping.
See
docs/axis-4-advanced.mdfor the mapping rule and definitions. SeeDOCUMENTATION.mdsection 7 (Axis 4) for the rationale.
id (required): Task IDRead task_info.md — specifically the Context Scope label from step 06.
Update progress.md: step 07 status = "in-progress", Started = {timestamp ISO 8601}.
Read the context_scope label set in step 06. Apply this deterministic mapping:
| Context Scope | Advanced | |---|---| | diff | False | | file | False | | repo | True (select the specific beyond-diff category) | | external | True (select the specific beyond-diff category) |
You do not need to evaluate Axis 3 and Axis 4 separately. Once Context Scope is determined, Advanced is automatic.
Why this mapping works: Axis 4 asks whether the comment requires knowledge beyond the files changed in the PR. The files touched by the PR include the changed lines (the diff) and the unchanged lines of those same files. Diff and File are within the PR's files, so Advanced is False. Repo and External are outside the PR's files, so Advanced is True.
If Context Scope is repo or external, select the category that best explains why:
| Category (platform value) | What to look for | |---|---| | Repo-specific conventions | Pertains to conventions, patterns, or architectural decisions specific to this repo. | | Context outside changed files | Requires knowledge from files not touched by the PR. | | Recent language/library updates | Requires awareness of recent or non-obvious language/framework behavior. | | Better implementation approach | Suggests a fundamentally better design, algorithm, or API usage (not just style). |
If more than one category applies, pick the primary driver.
Document in 1-2 sentences:
Add to the Labels section:
### Advanced
- **Label:** {Repo-specific conventions | Context outside changed files | Recent language/library updates | Better implementation approach | False}
- **Reasoning:** {1-2 sentences explaining the mapping derivation}
Update progress.md: step 07 status = "done", Completed = {timestamp ISO 8601}, Current Step = 08 - Generate Output.
testing
step-09-recheck
development
# step-08-generate-output ## What it does Compiles all four axis labels into the final JSON output, validates consistency, and generates the deliverable file ready for submission. ## Prerequisites - Steps 04-07 completed (all four axes labeled) ## Context > See `docs/steps/step10.md` for the submission checklist. ## Arguments - `id` (required): Task ID ## Instructions ### 1. Recover context Read `task_info.md` — extract all four labels and their reasoning from the Labels section. Update
documentation
# step-06-label-context-scope ## What it does Labels Axis 3 — Context Scope. Determines what level of context a reviewer would need to confidently make this comment and documents all evidence used. ## Prerequisites - Step 05 completed (Severity labeled) ## Context > See `docs/axis-3-context-scope.md` for definitions, evaluation criteria, and examples. > See `docs/steps/step8.md` for the step-by-step process. > See `DOCUMENTATION.md` sections 8 (FAQ), 9 (Common Mistakes), and 10 (Tips) for edg
testing
# step-05-label-severity ## What it does Labels Axis 2 — Severity. Assesses how severe the issue is that the review comment points out. ## Prerequisites - Step 04 completed (Quality labeled) ## Context > See `docs/axis-2-severity.md` for definitions, evaluation criteria, and examples. > See `docs/steps/step7.md` for the step-by-step process. > See `DOCUMENTATION.md` sections 8 (FAQ), 9 (Common Mistakes), and 10 (Tips) for edge cases and pitfalls. **Critical reminder:** Severity measures the