Conversation
|
Hi @desmondwong1215, thank you for your contribution! 🎉 This PR comes from your fork Before you request for a review, please ensure that you have tested your changes locally! Important The previously recommended way of using Please read the following instructions for the latest instructions. PrerequisitesEnsure that you have the Testing stepsIf you already have a local Git-Mastery root to test, you can skip the following step. Create a Git-Mastery root locally: gitmastery setupNavigate into the Git-Mastery root (defaults to cd gitmastery-exercises/Edit the {
# other fields...
"exercises_source": {
"username": "desmondwong1215",
"repository": "exercises",
"branch": "agent"
}
}Then, you can use the gitmastery download <your new change>
gitmastery verifyChecklist
Important To any reviewers of this pull request, please use the same instructions above to test the changes. |
There was a problem hiding this comment.
Pull request overview
This PR introduces an AI-facing documentation layer using the “Agent Skills” pattern, plus an AGENT.md entrypoint, to help AI tools and humans navigate and extend the Git-Mastery exercises repo.
Changes:
- Adds
AGENT.mddescribing how AI agents should load and combine skills for different tasks. - Introduces structured skills under
.claude/skills/for project overview, exercise development, exercise utilities, and coding standards, including detailed sub-guides. - Documents the
exercise_utilsAPIs and common exercise/test patterns, with links into real code and example exercises.
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
AGENT.md |
Defines the top-level AI agent workflow and maps user tasks to the new skills. |
.claude/skills/project-overview/SKILL.md |
Provides a high-level repo overview, exercise types, conventions, and links to other skills (some links currently point to missing docs/skills). |
.claude/skills/exercise-utils/SKILL.md |
Central index and quick-reference for the exercise_utils package, with examples and module dependency diagram (testing skill link is broken). |
.claude/skills/exercise-utils/git-module.md |
Documents the exercise_utils.git wrapper functions and their responsibilities. |
.claude/skills/exercise-utils/github-module.md |
Documents exercise_utils.github_cli helpers, but currently shows an incorrect clone_repo_with_gh signature. |
.claude/skills/exercise-utils/cli-module.md |
Describes the CLI execution helpers (run, run_command, run_command_no_exit) and where they’re used. |
.claude/skills/exercise-utils/file-module.md |
Documents file utility helpers and how they auto-create directories/dedent content. |
.claude/skills/exercise-utils/gitmastery-module.md |
Describes create_start_tag() and when to use it versus test helpers. |
.claude/skills/exercise-utils/test-module.md |
Summarizes the test loader and helpers, but shows an incorrect GitAutograderStatus.SUCCESS enum in the example. |
.claude/skills/exercise-development/SKILL.md |
Top-level guide for creating/modifying exercises, but its contract for standard exercises (download.py with __requires_*__ and download()) is out of sync with current tooling (.gitmastery-exercise.json + setup()), references a non-existent remote_branch_pull/ exercise, and links to a missing testing skill. |
.claude/skills/exercise-development/standard-exercises.md |
Deep-dive guide for standard exercises, including scaffolding, patterns, and testing; shares the same outdated assumptions about download.py entrypoints/flags. |
.claude/skills/exercise-development/hands-on-scripts.md |
Detailed guide for creating hands-on scripts, aligned with current hands_on/* patterns and scripts/test-download.py. |
.claude/skills/coding-standards/SKILL.md |
Captures style, naming, type-hint, and best-practice guidance, but also links to a non-existent testing skill. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@desmondwong1215 Please rename |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 13 out of 13 changed files in this pull request and generated 13 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Constants at top**: Module-level `UPPER_CASE` | ||
|
|
||
| ## Common Mistakes to Avoid | ||
| - ❌ Calling `git` directly instead of using exercise_utils/git.py |
There was a problem hiding this comment.
Should we remove emojis from these files? Seems to be additional tokens to the context
|
|
||
| ### 1. Create Script File | ||
|
|
||
| Simply create a new `.py` file in the `hands_on/` directory: |
There was a problem hiding this comment.
While this is not entirely wrong, we can also use the new.sh script to generate a new hands on, which do you think is better?
There was a problem hiding this comment.
I think it is better to follow the standard workflow.
There was a problem hiding this comment.
I think this skill can be omitted, doesn't seem to be a "skill" for the agent
There was a problem hiding this comment.
I think this shouldnt be a "skill" for the agent, it should come under AGENTS.md directly, it is more of an instruction to the agent rather than a specific "skill"
AGENTS.md
Outdated
| - **Using utilities?** → `exercise-utils` (standalone) | ||
| - **Code review?** → `coding-standards` (standalone) | ||
|
|
||
| ## For Human Developers |
There was a problem hiding this comment.
No need to include this in AGENTS.md, it should be solely for AI context, not human developers
jovnc
left a comment
There was a problem hiding this comment.
LGTM let's merge this in and see if it helps, can always revert as its non-critical as well
Adds
skillswith AI-optimized documentation following Agent Skills standard.Structure:
project-overview,exercise-development,exercise-utils,coding-standards