You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/usethis-cli-modify/SKILL.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Modify the usethis CLI layer (commands, options, help text) and kee
4
4
compatibility: usethis, Python, typer, markdown
5
5
license: MIT
6
6
metadata:
7
-
version: "1.0"
7
+
version: "1.1"
8
8
---
9
9
10
10
# Modifying the CLI
@@ -34,6 +34,20 @@ After making CLI changes, review and update each of the following as needed:
34
34
35
35
The command reference page documents every command with its full description, supported options, and behavior. Update it to match any changes you made to commands, options, defaults, or descriptions.
36
36
37
+
Keep descriptions **factual and concise**. The reference is not the place for extended rationale, usage tips, or explanations of why an option exists. If important context is needed, put it in a separate documentation page and link to it from the reference.
38
+
39
+
Good — factual, concise:
40
+
41
+
```markdown
42
+
-`--output-file` to write the output to a file instead of stdout.
43
+
```
44
+
45
+
Bad — excessive rationale embedded in the reference:
46
+
47
+
```markdown
48
+
-`--output-file` to write the output to a file instead of stdout. This is useful to avoid issues when shell redirects (e.g. `> file.txt`) create the file before the command runs, which can influence the behaviour of `usethis show`.
49
+
```
50
+
37
51
### Command overview
38
52
39
53
The command overview page lists all commands organized by category with brief descriptions. Update it if you added, removed, renamed, or recategorized a command.
@@ -21,3 +21,7 @@ Note that we are interested in both errors and warnings from these tools - we sh
21
21
## When to run these checks
22
22
23
23
Before submitting changes for review, **always** run these static checks. This should be done every time, even for small changes, to avoid slowing down the code review process unnecessarily.
24
+
25
+
## What to do when prek checks fail
26
+
27
+
It's quite common for minor cosmetic changes to be made automatically when running the prek checks, even by linters such as Ruff and mkdownlint-cli2. Since auto-fixes may have been applied during the first run, if checks fail, you should re-run a second time to see if any issues remain. Only then should you proceed to fix any remaining issues manually.
This adds the skill entry to `skills-lock.json`. Multiple skills may be added from a single source.
44
+
**Warning:**`--skill '*'` installs _every_skill from the source repository, which can be hundreds of unwanted skills. Always prefer `--skill '<skill-name>'` unless you genuinely want all of them.
|`codspeed-optimize`|`CodSpeedHQ/codspeed`| Optimize code for performance using CodSpeed benchmarks and flamegraphs |
49
+
|`codspeed-setup-harness`|`CodSpeedHQ/codspeed`| Set up performance benchmarks and the CodSpeed harness for a project |
50
+
|`find-skills`|`vercel-labs/skills`| Discover and install agent skills from the open skills ecosystem for new capabilities |
50
51
51
52
### Important Instructions about Skills usage
52
53
53
54
- ALWAYS use possibly relevant agent skills when they are available. Eagerly use skills, if in doubt, assume a skill is relevant.
55
+
- ALWAYS use `find-skills` to research new skill capabilities if there are difficult tasks, tasks in an unfamiliar domain, if you believe there is a lack of clarity or direction around precisely how to proceed, or if you get stuck or find something surprisingly challenging. When using this skill, please be sure to use the `usethis-skills-external-install` skill when deciding to install a new external skill.
54
56
- ALWAYS consider the `usethis-qa-static-checks` to be relevant: if you think your task
55
57
is complete, always run this skill to check for any issues before finishing.
56
58
- ALWAYS mention which skills you've used after completing any task, in PR descriptions, and comments.
59
+
60
+
## Lessons
61
+
62
+
When you are working on a problem, you are almost always going to encounter a difficulty. This is great - it's an opportunity for learning. ALWAYS make a note explicitly of what lessons you are drawing as you complete a task or when receiving user feedback. Try and keep this structured: consider the root cause of the difficulty, and how you overcame it. After finishing work on a task, report back all your lessons. Finally, try and update the relevant skills with any new insights you've drawn, to help future agents, and/or create a new skill.
Copy file name to clipboardExpand all lines: docs/cli/reference.md
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -457,7 +457,28 @@ Currently supported subcommands:
457
457
458
458
-`usethis show backend` to show the inferred project manager backend, e.g. 'uv' or 'none'. This is the default backend used, i.e. when `--backend=auto` is specified.
459
459
-`usethis show name` to show the name of the project.
460
-
-`usethis show sonarqube` to show appropriate contents of a `sonar-projects.properties` file for SonarQube analysis.
460
+
-`usethis show sonarqube` to show appropriate contents of a `sonar-project.properties` file for SonarQube analysis.
461
+
462
+
### `usethis show sonarqube`
463
+
464
+
Show the contents of a `sonar-project.properties` file for SonarQube analysis.
465
+
466
+
If a `sonar-project.properties` file already exists in the project root, its contents are returned as-is. In this case, the `--project-key` option and `tool.usethis.sonarqube.project-key` in `pyproject.toml` are both ignored.
467
+
468
+
If no `sonar-project.properties` file exists, the contents are constructed from `pyproject.toml` configuration. In this case, a project key is required:
469
+
470
+
- If `--project-key` is provided, it is used.
471
+
- Otherwise, `tool.usethis.sonarqube.project-key` from `pyproject.toml` is used.
0 commit comments