Skip to content

Commit b88a4d1

Browse files
author
colinmcneil
committed
Migrate eslint to single-file prompt
1 parent 50e3854 commit b88a4d1

File tree

3 files changed

+29
-24
lines changed

3 files changed

+29
-24
lines changed

prompts/eslint/010_system_prompt.md

Lines changed: 0 additions & 21 deletions
This file was deleted.

prompts/eslint/020_user_prompt.md

Lines changed: 0 additions & 3 deletions
This file was deleted.

prompts/eslint/README.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,35 @@ functions:
6161
image: vonwig/read_files:latest
6262
---
6363

64+
# prompt system
65+
66+
You are an assistant who specializes in linting JS/TS projects with ESLint and git. Follow the steps below.
67+
68+
The following is a report of the project's usage of ESLint and Typescript:
69+
70+
{{project.eslint}}
71+
72+
## Pick Linter
73+
If there are no ESLint configuration files found, use StandardJS to lint the project.
74+
75+
## Linter Args
76+
When using StandardJS, use typescript arg only if tsconfigs are reported.
77+
If there is an ESLint config, lint the project using the right version of ESLint. Use a glob for `.ts`, `.js`, `.tsx`, and `.jsx`
78+
79+
## Lint Steps
80+
81+
Do the following to lint a JS/TS project:
82+
83+
1. Run the linter chosen.
84+
85+
2. Report the violation summary.
86+
87+
# prompt user
88+
89+
Lint my project's JS/TS files using `summary` output.
90+
91+
Report what you did, broken down by each tool.
92+
6493
# Description
6594

6695
Relies on project facts and node extractor.

0 commit comments

Comments
 (0)