Skills
clins1994/skills · sample text, made up
Four agent skills for writing on GitHub and Linear. People read the lead. The collapsed block holds the full text for agents, or for anyone who wants everything. Pick a skill to see what it writes. Click a block to open it.
The writing format. A lead people read, then the full text in a collapsed block for agents. It writes in your languages: a lead language and any others under it, saved once as your default. Change them for one post in plain words. The other skills use it for their text.
First run
/clins:postWith no default saved, it asks once, in the agent's own question UI, and saves one line to your agent's global instructions file. No language codes needed.
clins:post languages: lead english; also japanese. To change it, just tell me, for example: change my post languages to portuguese and japanese.PR comment, English only
/clins:postThe default. One lead that says what changed and what the reader must do, then one collapsed block.
@mika-tanaka
Fixed the retry bug in a3f91c2. Uploads now stop after 3 tries instead of looping. Please review the backoff values.
🇬🇧 More detailscollapsed
What changed
upload/retry.tscounts attempts per file, not per batch.- The backoff is 1 s, 4 s, then 9 s. After the third failure, the job reports
UPLOAD_GAVE_UP.
How it was tested
pnpm test upload: 42 passed.- Pulled the network cable during a 300 MB upload. The job stopped after 14 s.
PR comment, japanese first
/clins:post japanese firstThe default is english. For a team that reads japanese, ask for japanese first. English is still the original, so it comes after 原文:. There is one collapsed block per language, and both blocks say the same thing.
a3f91c2で再試行のバグを直しました。アップロードは3回で止まります。待ち時間の値を見てください。
原文: Fixed the retry bug in a3f91c2. Uploads now stop after 3 tries. Please review the backoff values.
🇯🇵 詳細collapsed
変更点
upload/retry.tsで、試行回数をファイルごとに数える。- 待ち時間は1秒、4秒、9秒。3回失敗したら
UPLOAD_GAVE_UPを返す。
🇬🇧 More detailscollapsed
Changes
upload/retry.tscounts attempts per file.- The backoff is 1 s, 4 s, then 9 s. After 3 failures, it returns
UPLOAD_GAVE_UP.
Short post
/clins:postWhen the details would only repeat the lead, the post is the lead alone. It has no divider, block or footer.
Fixed in b72e019. Please review again.
Creates a reviewable pull request: exact range, checks, title, before/after images under the lead, and the body from clins:post. Works with any host skill. Writes in your languages from clins:post.
PR description with before/after images
/clins:create-prThe images go between the lead and the divider, so a reviewer sees the change before opening anything. The review bot's section stays below the footer, unedited.
mainauth: show an error on a wrong password #128
A wrong password now shows "Wrong email or password" under the form. Please check the copy and the error color in dark mode.
| Before | After |
|---|---|
| A wrong password shows nothing. | A wrong password shows an error. |
🇬🇧 More detailscollapsed
Summary
The sign-in form shows the API's 401 as an inline error under the password field.
Why
Users retried 4 times on average before they reset their password (support ticket ENG-412).
Changes
LoginForm.vuereadserror.codeand shows the message.- New string
auth.wrongCredentialsinen.json.
How it was tested
pnpm test:e2e login: 6 passed.
Not tested (and why)
- Safari 16. No device available.
Screenshots
At the top. Chrome, 1280×800, base 9c1e0d4, head a3f91c2.
PR description in more than one language
mainauth: show an error on a wrong password #128
Posts to GitHub with gh: PR bodies with attached images, PR comments, replies in review threads, and issues.
Reply in a review thread
/clins:github replyThe reply goes inside the reviewer's thread, not as a new comment at the bottom. A fix usually needs only a short post.
This waits 0 ms on the first attempt. Is that intended?
No. Fixed in c41d9e0: the first retry now waits 1 s. Please resolve if this looks right.
GitHub issue
/clins:github issueIssues use the same format, with Context, Work and Done when inside the block.
Stop retrying uploads after 3 attempts #131
Large uploads retry forever when the network drops. Cap the retries at 3. This is done when the job reports UPLOAD_GAVE_UP.
🇬🇧 More detailscollapsed
Context
upload/retry.ts counts attempts per batch, so one bad file resets the counter.
Work
- Count attempts per file.
- Back off 1 s, 4 s, then 9 s.
Done when
- A test pulls the network mid-upload and sees
UPLOAD_GAVE_UPafter 3 tries.
Posts to Linear: new issues with fields, safe description updates, comments, and replies in threads.
Linear issue
/clins:linear issueThe same format on Linear. The collapsible block uses Linear's >>> syntax instead of <details>.
Show an error on a wrong password
The sign-in form shows nothing when the password is wrong. Add an inline error. This is done when the e2e test for a wrong password passes.
🇬🇧 More details
Context
The API returns 401 with code: "wrong_credentials". The form ignores it.
Work
- Show the message under the password field.
- Add the string to
en.json.
Done when
pnpm test:e2e logincovers a wrong password and passes.
Linear issue, english and japanese
/clins:linear issue, japanese as wellThe default is english. "Japanese as well" adds a japanese lead under the english one, and a second block. English leads because it is the original.
Show an error on a wrong password
The sign-in form shows nothing when the password is wrong. Add an inline error. This is done when the e2e test for a wrong password passes.
パスワードが違うと、サインインフォームに何も表示されません。エラーをフォーム内に表示してください。間違ったパスワードのe2eテストが通れば完了です。
🇬🇧 More details
Context
The API returns 401 with code: "wrong_credentials". The form ignores it.
Work
- Show the message under the password field.
- Add the string to
en.json.
Done when
pnpm test:e2e logincovers a wrong password and passes.
🇯🇵 詳細
背景
APIは401とcode: "wrong_credentials"を返す。フォームはこれを無視している。
やること
- パスワード欄の下にメッセージを表示する。
en.jsonに文字列を追加する。
完了条件
pnpm test:e2e loginが間違ったパスワードのケースを含み、成功する。
Linear comment and thread reply
/clins:linear replyA reply stays in its thread. When the details would only repeat the lead, the reply is just the lead.
Does this also cover the reset-password form?
Not yet. I filed ENG-436 for the reset form, so this issue can close when the sign-in error ships.